| Author |
Message
|
| ruimadaleno |
 Posted: Fri Jul 18, 2014 1:10 am Post subject: Duplicate schema in WSDL after service deploy in Broker |
 |
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
i have deployed a service in QUA (staging) environment.
When the service was deployed in PROD (production) environment the schemas referred in the wsdl got duplicated 
http://1drv.ms/1n0lOHQ
Please check the image in the link above. It contains a screenshot from soapui showing service definitions in both environments.
In the left side we can see the service definition (wsdl) in the QUA environent. In the right side of the image we can see the service definition in the PROD environment. Note the duplication on types defined in schema (apoliceType,DossierClinicoTypeBPM ,etc)
Please note: the same bar file was used to deploy the service in both environments.
I'll open a PMR to investigate this behaviour of broker deployment but i'd like to ear from your experience on this subject. Is this a know issue ? do i get some info in log files regarding this issue ?
Both environments are running in
windows 2008 R2 enterprise
broker 8.0.0.3
best regards
Rui Madaleno
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jul 18, 2014 5:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Could it be that in production you have the schema once in the application and once in the library? Are you sure that all your production artifacts are at the same release level than the corresponding QA artifacts?
Are you deploying as an application or as independent resources?
Remember with message sets you could have the same xsds in multiple message sets. This is no longer the case with message models and having the same xsds in multiple libraries can be detrimental when the libraries are loaded in the same (application/default) container.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Fri Jul 18, 2014 8:22 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi fjb_saper,
we are deploying a Service which indeed uses a library. But the service is the only one with XSDs. The library only has some ESQL files.
We deploy the application in a .BAR file, which is exactly the same release as the one in staging so i'm sure that all production artifacts are exactly at the same release level than the corresponding QA artfacts .
We have deployed the bar file again and the reported behaviour has gone we see no duplication of schemas in wsdl 
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Mon Nov 03, 2014 4:02 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
Sorry to bring this thread to live from the dead (halloween hangover ..  LOL)
PMR was open but so far IBM cannot find the problem/solution.
Any help/ideas/investigation directions ? this issue is hitting our production environment, and it occurs sporadically.
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 03, 2014 7:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It sounds as much like a display problem as an actual issue.
But that's because it's not clear if you are otherwise seeing production issues because of the duplicated schemas?
It could also be that someone is deploying the schemas separately or etc. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Fri Jan 23, 2015 7:23 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
a long time has passed since i reported this issue (several months ) but IBM just can't get this problem solved , we suffer from several unavailabilities in prodution environment, and i am opening this thread to get some help from you guys. 
Let's recap the issue:
a. The error reported (CWLLG1144E ) is only seen in BPM Plataform. we cannot find this error in broker log files. This error is not returned to BPM from Broker service. As far as I understand BPM application asks for WSDL from broker service and validates it. When the issue arises, this validation fails and bpm throws the error CWLLG1144E. Please note that the service is not called (we don't see service request in monitoring info - record and replay in action here), BPM just fails to validate service wsdl BEFORE it tries to call the service itself. The full message of the error is bellow on this thread.
b. When the issue arises, the server is available and responsive . Other applications (built with non BPM technology) like SOAP clients (SOAPUI) can call the service and get the expected responses containing business data.
c. We are not able to reproduce the problem with tools like SOAPUI. When the issue arises we can successfully call the service with SOAPUI , but we will never see the CWLLG1144E because neither broker nor soapui validate the WSDL. This validation (and the error) is made by BPM Plataform. The point here is: Broker is presenting to consumers throughout WSDL , why is this WSDL distinct from the “original” (deployed) WSDL ? what causes the broker to publish a service WSDL that contains a lot of XSD files that are not present at deploy time ?
| Code: |
Ocorreu um erro de tempo de execução no script ("Process: 'Catch Error' ProcessItem: 'Validate Exception' Type: 'ITEM'" -1:-1).java.lang.RuntimeException: CWLLG1144E: Não é possível validar a WSDL para o serviço : {http://www.contact admin.pt/PrismaSinistros}PrismaSinistrosHttpService
<br/> at com.ibm.bpm.ws.jaxws.validator.ValidatorImpl.validateandPopulateCache(ValidatorImpl.java:379)
<br/> at com.ibm.bpm.ws.jaxws.validator.ValidatorImpl.validate(ValidatorImpl.java:113)
<br/> at com.ibm.bpm.ws.jaxws.connector.SOAPConnector.createServiceClient(SOAPConnector.java:218)
<br/> at com.ibm.bpm.ws.jaxws.connector.SOAPConnector.execute(SOAPConnector.java:136)
<br/> at com.lombardisoftware.component.wsconnector.worker.WSConnectorWorker.doJob(WSConnectorWorker.java:123)
<br/> at com.lombardisoftware.component.common.workflow.ExecutionJob.doJob(ExecutionJob.java:409)
<br/> at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1278)
<br/> at com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.resumeTask(EJBWorkflowManagerBean.java:353)
<br/> at com.lombardisoftware.server.ejb.workflow.EJSRemoteStatefulEJBWorkflowManager_82478d70.resumeTask(Unknown Source)
<br/> at com.lombardisoftware.server.ejb.workflow._EJBWorkflowManagerInterface_Stub.resumeTask(_EJBWorkflowManagerInterface_Stub.java:347)
<br/> at com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegateDefault.resumeTask(EJBWorkflowManagerDelegateDefault.java:105)
<br/> at com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegateWebSphere$2.run(EJBWorkflowManagerDelegateWebSphere.java:52)
<br/> at java.security.AccessController.doPrivileged(AccessController.java:327)
<br/> at com.lombardisoftware.client.delegate.common.WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive(WebsphereDelegateHelper.java:197)
<br/> at com.lombardisoftware.client.delegate.common.WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive(WebsphereDelegateHelper.java:181)
<br/> at com.lombardisoftware.component.common.workflow.EJBWorkflowManagerDelegateWebSphere.resumeTask(EJBWorkflowManagerDelegateWebSphere.java:50)
<br/> at com.lombardisoftware.component.common.web.WebWorkflowManager.callEJBWorkflowManager(WebWorkflowManager.java:820)
<br/> at com.lombardisoftware.component.common.web.WebWorkflowManager.processScreen(WebWorkflowManager.java:786)
<br/> at com.lombardisoftware.component.common.web.WebWorkflowManager.processRequest(WebWorkflowManager.java:319)
<br/> at com.lombardisoftware.servlet.AjaxControllerServlet.doPost(AjaxControllerServlet.java:142)
<br/> at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
<br/> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
<br/> at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230)
<br/> at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)
<br/> at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
<br/> at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97)
<br/> at com.lombardisoftware.servlet.CachingFilter.doFilter(CachingFilter.java:57)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.lombardisoftware.servlet.ClearThreadCachesFilter.doFilter(ClearThreadCachesFilter.java:34)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.lombardisoftware.servlet.SetUserTimeZoneFilter.doFilter(SetUserTimeZoneFilter.java:59)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.lombardisoftware.servlet.BidiSupportFilter.doFilter(BidiSupportFilter.java:50)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.lombardisoftware.servlet.CrossSiteScriptingFilter.doFilter(CrossSiteScriptingFilter.java:83)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.lombardisoftware.servlet.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:35)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.lombardisoftware.servlet.CompressionFilter.doFilter(CompressionFilter.java:55)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.ibm.bpm.servlet.filters.GenericSecurityServletFilter.doFilter(GenericSecurityServletFilter.java:84)
<br/> at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:960)
<br/> at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1064)
<br/> at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
<br/> at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:914)
<br/> at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
<br/> at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
<br/> at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453)
<br/> at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
<br/> at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306)
<br/> at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:84)
<br/> at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
<br/> at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
<br/> at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
<br/> at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
<br/> at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
<br/> at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
<br/> at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
<br/> at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
<br/> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1702)
<br/>Caused by: com.lombardisoftware.core.xml.schema.xs.XSException: :file:/C:/Windows/TEMP/tw-schema-2736486023230826537.xsd:file:/C:/Windows/TEMP/tw-schema-2736486023230826537.xsd::8:41:851:sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'DossierClinicoTypeBPM,DossierClinico'.
<br/> at com.lombardisoftware.core.xml.schema.xs.XSLoader.loadGrammar(XSLoader.java:175)
<br/> at com.lombardisoftware.core.xml.schema.xs.XSLoader.load(XSLoader.java:159)
<br/> at com.lombardisoftware.server.eai.soap.wsdl.WSDLHelper.loadSchema(WSDLHelper.java:344)
<br/> at com.lombardisoftware.server.eai.soap.wsdl.WSDLHelper.loadSchema(WSDLHelper.java:251)
<br/> at com.lombardisoftware.server.eai.soap.wsdl.TWWSDLDataBuilder.buildWSDLDataImpl(TWWSDLDataBuilder.java:352)
<br/> at com.lombardisoftware.server.eai.soap.wsdl.TWWSDLDataBuilder.buildWSDLMetaDataContext(TWWSDLDataBuilder.java:333)
<br/> at com.ibm.bpm.ws.jaxws.validator.ValidatorImpl.validateandPopulateCache(ValidatorImpl.java:346)
<br/> ... 70 more
<br/>Caused by: :file:/C:/Windows/TEMP/tw-schema-2736486023230826537.xsd:file:/C:/Windows/TEMP/tw-schema-2736486023230826537.xsd::8:41:851:sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'DossierClinicoTypeBPM,DossierClinico'.
<br/> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
<br/> at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown Source)
<br/> at org.apache.xerces.impl.xs.traversers.XSDHandler.checkForDuplicateNames(Unknown Source)
<br/> at org.apache.xerces.impl.xs.traversers.XSDHandler.buildGlobalNameRegistries(Unknown Source)
<br/> at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source)
<br/> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)
<br/> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
<br/> at com.lombardisoftware.core.xml.schema.xs.XSLoader.loadGrammar(XSLoader.java:173)
<br/> ... 76 more
<br/><br/>
|
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| robhenley |
| Posted: Fri Jan 23, 2015 9:04 am Post subject: |
|
|
Newbie
Joined: 03 Mar 2006
Posts: 5
|
Hi Rui, can you give the PMR number please? Thanks!
_________________
Rob |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Mon Jan 26, 2015 3:49 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| robhenley wrote: |
| Hi Rui, can you give the PMR number please? Thanks! |
Hi Rob, this is it: PMR 40971,001,822
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed Apr 01, 2015 8:49 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
no luck with PRM so far
we are still sending trace files to ibm support. No clue what is causing the error.
This error is hitting all our environments (PROD, QUA, DEV) and it is limited to a set of message flows developed for a project (we have several other message flows where this errors was not detected so far), so we start to suspect that something in the message flows implementation is causing the issue.
bellow you can see a picture of a soapui project , showing a WSDL that contains > 120 xsd !!!
http://1drv.ms/1GgQBJT
Any directions on issue investigation ?
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 01, 2015 7:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Just as a question. If you use a browser and send the request for the wsdl to the broker, was happens then?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Thu Apr 02, 2015 1:53 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
hello fjb_saper,
using any kind of browser (Ie, mozilla, chrome) i can navigate to service (message flow) wsdl address. successfully.
An example: the service "PrismaRecibos" is not healthy (presenting the symptoms reported in PMR). I can get the wsdl
http://10.48.48.130:7800/PrismaRecibos/PrismaRecibos?wsdl
| Code: |
<wsdl:definitions name="PrismaRecibos" targetNamespace="http://www.contact admin.pt/PrismaRecibos">
<wsdl:documentation>
<wsdl:appinfo source="WMQI_APPINFO">
<MRWSDLAppInfo imported="true">
<binding hasEncoding="false" imported="true" name="PrismaRecibosHttpBinding" originalBindingStyle="document"/>
</MRWSDLAppInfo>
</wsdl:appinfo>
</wsdl:documentation>
<wsdl:types>
<xsd:schema targetNamespace="http://www.contact admin.pt/PrismaRecibos">
<xsd:include schemaLocation="http://10.48.48.130:7800/PrismaRecibos/PrismaRecibos?xsd=xsd0"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="createReciboIndemnizacaoRequestMsg">
<wsdl:part element="tns:CreateReciboIndemnizacao" name="createReciboIndemnizacaoParameters"/>
</wsdl:message>
<wsdl:message name="createReciboIndemnizacaoResponseMsg">
<wsdl:part element="tns:CreateReciboIndemnizacaoResponse" name="createReciboIndemnizacaoResult"/>
</wsdl:message>
<wsdl:message name="getReciboIndemnizacaoRequestMsg">
<wsdl:part element="tns:GetReciboIndemnizacao" name="getReciboIndemnizacaoParameters"/>
</wsdl:message>
<wsdl:message name="getReciboIndemnizacaoResponseMsg">
<wsdl:part element="tns:GetReciboIndemnizacaoResponse" name="getReciboIndemnizacaoResult"/>
</wsdl:message>
<wsdl:message name="updateSituacaoReciboIndemnizacaoRequestMsg"><wsdl:part element="tns:UpdateSituacaoReciboIndemnizacao" name="updateSituacaoReciboIndemnizacaoParameters"/></wsdl:message><wsdl:message name="updateSituacaoReciboIndemnizacaoResponseMsg"><wsdl:part element="tns:UpdateSituacaoReciboIndemnizacaoResponse" name="updateSituacaoReciboIndemnizacaoResult"/></wsdl:message>
<wsdl:message name="SearchReciboIndemnizacaoRequestMsg"><wsdl:part element="tns:SearchReciboIndemnizacao" name="searchReciboIndemnizacaoParameters"/></wsdl:message>
<wsdl:message name="SearchReciboIndemnizacaoResponseMsg"><wsdl:part element="tns:SearchReciboIndemnizacaoResponse" name="searchReciboIndemnizacaoResult"/></wsdl:message>
<wsdl:portType name="PrismaRecibos">
<wsdl:operation name="CreateReciboIndemnizacao">
<wsdl:input message="tns:createReciboIndemnizacaoRequestMsg" name="createReciboIndemnizacaoRequest"/>
<wsdl:output message="tns:createReciboIndemnizacaoResponseMsg" name="createReciboIndemnizacaoResponse"/></wsdl:operation>
<wsdl:operation name="GetReciboIndemnizacao">
<wsdl:input message="tns:getReciboIndemnizacaoRequestMsg" name="GetReciboIndemnizacaoRequest"/>
<wsdl:output message="tns:getReciboIndemnizacaoResponseMsg" name="GetReciboIndemnizacaoResponse"/></wsdl:operation>
<wsdl:operation name="UpdateSituacaoReciboIndemnizacao">
<wsdl:input message="tns:updateSituacaoReciboIndemnizacaoRequestMsg" name="UpdateSituacaoReciboIndemnizacaoRequest"/>
<wsdl:output message="tns:updateSituacaoReciboIndemnizacaoResponseMsg" name="UpdateSituacaoReciboIndemnizacaoResponse"/></wsdl:operation>
<wsdl:operation name="SearchReciboIndemnizacao">
<wsdl:input message="tns:SearchReciboIndemnizacaoRequestMsg" name="SearchReciboIndemnizacaoRequest"/>
<wsdl:output message="tns:SearchReciboIndemnizacaoResponseMsg" name="SearchReciboIndemnizacaoResponse"/></wsdl:operation></wsdl:portType>
<wsdl:binding name="PrismaRecibosHttpBinding" type="tns:PrismaRecibos">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="CreateReciboIndemnizacao"><soap:operation soapAction="http://www.contact admin.pt/PrismaRecibos/CreateReciboIndemnizacao"/><wsdl:input name="createReciboIndemnizacaoRequest">
<soap:body use="literal"/></wsdl:input><wsdl:output name="createReciboIndemnizacaoResponse">
<soap:body use="literal"/></wsdl:output></wsdl:operation>
<wsdl:operation name="GetReciboIndemnizacao"><soap:operation soapAction="http://www.contact admin.pt/PrismaRecibos/GetReciboIndemnizacao"/>
<wsdl:input name="GetReciboIndemnizacaoRequest">
<soap:body use="literal"/></wsdl:input>
<wsdl:output name="GetReciboIndemnizacaoResponse"><soap:body use="literal"/></wsdl:output></wsdl:operation>
<wsdl:operation name="UpdateSituacaoReciboIndemnizacao">
<soap:operation soapAction="http://www.contact admin.pt/PrismaRecibos/UpdateSituacaoReciboIndemnizacao"/><wsdl:input name="UpdateSituacaoReciboIndemnizacaoRequest">
<soap:body use="literal"/></wsdl:input><wsdl:output name="UpdateSituacaoReciboIndemnizacaoResponse"><soap:body use="literal"/></wsdl:output></wsdl:operation><wsdl:operation name="SearchReciboIndemnizacao"><soap:operation soapAction="http://www.contact admin.pt/PrismaRecibos/SearchReciboIndemnizacao"/><wsdl:input name="SearchReciboIndemnizacaoRequest"><soap:body use="literal"/></wsdl:input><wsdl:output name="SearchReciboIndemnizacaoResponse"><soap:body use="literal"/></wsdl:output></wsdl:operation></wsdl:binding><wsdl:service name="PrismaRecibosHttpService"><wsdl:port binding="tns:PrismaRecibosHttpBinding" name="PrismaRecibosHttpPort"><soap:address location="http://10.48.48.130:7800/PrismaRecibos/PrismaRecibos"/></wsdl:port></wsdl:service></wsdl:definitions>
|
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 02, 2015 5:02 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
I see you got the wsdl. Did you test it? Save the wsdl and see if it requires xsds that have not been included in the on the wire transmission.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rsk33 |
| Posted: Thu Apr 02, 2015 10:47 pm Post subject: |
|
|
Centurion
Joined: 21 Aug 2006
Posts: 141
|
hi
we are having services developed in broker. we have the issue duplication of the wsdls whenever we add new operation. Reported to IBM. No response till now.
but i got work around. Check the wsdl Application Info tag.
<wsdl:documentation>
<wsdl:appinfo source="WMQI_APPINFO">
<MRWSDLAppInfo imported="true">
<binding hasEncoding="false" imported="true" name="accountServicesHttpBinding" originalBindingStyle="document"/>
</MRWSDLAppInfo>
</wsdl:appinfo>
</wsdl:documentation>
There is one tag name generated after <MRWSDLAppInfo> imported="true"> missing . we are adding before create any new operation and regenerate binding. we do not any duplicates. This is weired. but try in your case works or not.
Regards |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Mon Apr 06, 2015 6:35 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| fjb_saper wrote: |
| I see you got the wsdl. Did you test it? Save the wsdl and see if it requires xsds that have not been included in the on the wire transmission. |
Hi fjb_saper,
i'm not sure if understand your suggestion 
I can get the wsdl , using a browser. Using a browser i can also get all xsd used (included) by the wsdl (http://10.48.48.130:7800/PrismaRecibos/PrismaRecibos?xsd=xsd0)
Using soapui i can extract (save to disk) wsdl and all xsd files.
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Tue Apr 07, 2015 3:32 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| rsk33 wrote: |
hi
we are having services developed in broker. we have the issue duplication of the wsdls whenever we add new operation. Reported to IBM. No response till now.
but i got work around. Check the wsdl Application Info tag.
| Code: |
<wsdl:documentation>
<wsdl:appinfo source="WMQI_APPINFO">
<MRWSDLAppInfo imported="true">
<binding hasEncoding="false" imported="true" name="accountServicesHttpBinding" originalBindingStyle="document"/>
</MRWSDLAppInfo>
</wsdl:appinfo>
</wsdl:documentation> |
There is one tag name generated after <MRWSDLAppInfo> imported="true"> missing . we are adding before create any new operation and regenerate binding. we do not any duplicates. This is weired. but try in your case works or not.
Regards |
Hi rsk33, no operations were added to message flows/service so i must be hitting another problem
thank you for you reply
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
|
|
