| Author |
Message
|
| ntwmb |
 Posted: Sat Apr 18, 2009 8:59 pm Post subject: WSDL - soapbinding problem |
 |
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Hello
My flow has three nodes soapinput compute soapreply, imported wsdl into toolkit, build the file and while deploying the flow it has given BIP3732S error, it is not able to recognise binding name in the messageset.
My WSDL file has got schema import statements, and the xsd files also have schema import statements.
I checked this wsdl in xmlspy, which showed it is valid.
Please see the link from IBM which tells about temporary fix related this issue,
If someone faced similar issue, please share your thoughts... |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Sun Apr 19, 2009 3:50 am Post subject: Re: WSDL - soapbinding problem |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| ntwmb wrote: |
Please see the link from IBM which tells about temporary fix related this issue |
Which link? Would you care to share it with us? |
|
| Back to top |
|
|
| ntwmb |
| Posted: Sun Apr 19, 2009 8:55 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Sun Apr 19, 2009 9:54 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| I had to take the comma off the end of the link, then it worked for me. |
|
| Back to top |
|
|
| atul_jain1981 |
| Posted: Mon Apr 20, 2009 3:15 am Post subject: |
|
|
Novice
Joined: 27 Apr 2008
Posts: 10
|
| can u plz provide more details about error msg u r getting |
|
| Back to top |
|
|
| ntwmb |
| Posted: Mon Apr 20, 2009 5:46 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
Please see the error details given below
BIP3732S: The message could not be found in resource bundle BIPv610. Inserts: OrderMessage /var/mqsi/components/9696344e-1a01-0000-0080-c2344f5f36c5/config/test/ordermessage.wsdl test http://test/services/orderservice {4} {5}
BIP3726S: The message could not be found in resource bundle BIPv610. Inserts: SOAP Input {1} {2} {3} {4} {5} |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 20, 2009 6:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| ntwmb |
| Posted: Mon Apr 20, 2009 6:45 am Post subject: |
|
|
Apprentice
Joined: 18 Sep 2008
Posts: 34
|
I have created the message set from the wsdl, and build the bar file, while deploying the bar file, I got these errors in the event log..
In the IBM link, it is mentioned that WDL cannot resolve the relative paths of xml import statements..
Is this the main problem that is causing my flow to fail? |
|
| Back to top |
|
|
| crossland |
| Posted: Wed Jan 20, 2010 1:17 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
|
| Back to top |
|
|
| crossland |
| Posted: Wed Jan 20, 2010 3:51 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
Interesting. There is only one google hit for BIP3732S and that is on this post, created yeaterday.
In my case, I have been getting the error after changing the namespace in my WSDL. However, the WSDL validates ok and generates a message set which deploys ok.
The problem happens when I deploy my message flow, even after creating a new message set project from the new WSDL and then using this to create a new SOAP input node.
The exact error is:
BIP3732S: The message could not be found in resource bundle BIPv610. Inserts: BS_GetContentElementList_V01_00 C:\Documents and Settings\All Users\Application Data\IBM\MQSI/components/BROKER/4123864b-2601-0000-0080-eabc10a53e88/config/XSD/BS_GetContentElementListMessageSet_V01/com/company/services/messages/party/bsgetcontentelementlist/v0100/BS_GetContent_V01_00.wsdl BS_GetContentElementListMessageSet_V01 http://company.com/Services/Messages/Party/BS_GetContentElementList/V01.00 {4} {5}
This is using 6.1.0.5 toolkit and broker on windows. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed Jan 20, 2010 11:37 am Post subject: Re: WSDL - soapbinding problem |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
It's usually less confusing to start a new topic, rather than to re-open an old one. The new topic can refer to the old one though.
| crossland wrote: |
The exact error is:
BIP3732S: The message could not be found in resource bundle BIPv610... |
It looks like the BIP error message catalogs are not properly installed. The error message for BIP3732 should be:
| Quote: |
BIP3732:
Message: The specified WSDL binding 'BS_GetContentElementList_V01_00' could not be found in the supplied WSDL file 'C:\Documents and Settings\All Users\Application Data\IBM\MQSI/components/BROKER/4123864b-2601-0000-0080-eabc10a53e88/config/XSD/BS_GetContentElementListMessageSet_V01/com/company/services/messages/party/bsgetcontentelementlist/v0100/BS_GetContent_V01_00.wsdl'.
Explanation: The WSDL binding 'BS_GetContentElementList_V01_00' from the target namespace 'http://company.com/Services/Messages/Party/BS_GetContentElementList/V01.00' associated with message set 'BS_GetContentElementListMessageSet_V01' was not found in the WSDL file 'C:\Documents and Settings\All Users\Application Data\IBM\MQSI/components/BROKER/4123864b-2601-0000-0080-eabc10a53e88/config/XSD/BS_GetContentElementListMessageSet_V01/com/company/services/messages/party/bsgetcontentelementlist/v0100/BS_GetContent_V01_00.wsdl'. This could be because the WSDL file is missing, invalid or corrupt.
Response: Determine the cause of the error and correct it. Ensure that the WSDL file is valid and that it validates correctly. |
The cause of the error is another matter, but here's a good place to start:
| mqjeff wrote: |
| Did you deploy the WSDL? |
|
|
| Back to top |
|
|
| crossland |
| Posted: Fri Jan 22, 2010 1:23 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
| crossland wrote: |
The problem happens when I deploy my message flow, even after creating a new message set project from the new WSDL and then using this to create a new SOAP input node.
|
|
|
| Back to top |
|
|
| crossland |
| Posted: Mon Feb 01, 2010 1:05 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
| For anyone else hitting this problem, it was resolved by fixing the WSDL. |
|
| Back to top |
|
|
|
|
