| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [Solved]Generating WSDL on broker to support 1.2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Hari |
 Posted: Thu Mar 07, 2013 5:23 pm Post subject: [Solved]Generating WSDL on broker to support 1.2 |
 |
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
The environment: Broker 7.0.0.3 on Windows.
We are exposing a message flow as a Webservice and the requirement is that the WSDL support SOAP 1.2.
But while generating the WSDL's on the broker, the drop-down for the "SOAP Version" is greyed out with "1.1"
Am I missing something here or is there a way we can generate WSDL's on broker to support SOAP 1.2
Appreciate your help.
Last edited by Hari on Mon Mar 25, 2013 12:53 pm; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Mar 08, 2013 2:20 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
import soap 1.2 xsd from the IBM defined list. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Hari |
| Posted: Fri Mar 08, 2013 10:29 am Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Mar 11, 2013 4:44 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Soap 1.1 is more reliably implemented. You might like to stay with 1.1. What features of 1.2 are you trying to use that 1.1 does not support?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Hari |
| Posted: Mon Mar 25, 2013 12:51 pm Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
Here are the updates from the PMR which we had opened:
1. Generate deployable WSDL from existing message set
2. Edit the generated WSDL with WSDL editor to add new SOAP1.2 binding
3. Export the updated WSDL to your local file system (keep all file
structure)
4. Import the step 3 WSDL. Select SOAP1.2 binding and choose to
over write exiting files during importing.
The reason why we have to re-import is, the newly added SOAP1.2 binding
cannot be recognized by toolkit and runtime. In step 3, the export will
copy the WSDL file and all referenced schema files (*.mxsd) to the local
file system (the mxsd file will be saved as xsd file). When you
re-import, the xsd files will be copied back as mxsd file, the content
and the folder structure will NOT be changed. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
