| Author |
Message
|
| Risto |
 Posted: Fri May 22, 2009 4:53 am Post subject: xsi types in output xml |
 |
|
Newbie
Joined: 29 Apr 2009
Posts: 6
|
Hi All,
I am trying to call a webservice. I have created my message set from the WSDL. The web service expects to have the the types in the xml message as follows.
<arrayOfProspect_1 soapenc:arrayType="ns2:Prospect[2]" xsi:type="soapenc:Array">
All that I get on my output xlm is
<arrayOfProspect_1>
How can I get the types to be included in the output xml. My message is in the MRM domain. BTW, although I have used WMB for a while this is my first time trying to call a web service.
Thanks. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri May 22, 2009 5:26 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Which version of message broker runtime? |
|
| Back to top |
|
|
| Risto |
| Posted: Fri May 22, 2009 5:35 am Post subject: |
|
|
Newbie
Joined: 29 Apr 2009
Posts: 6
|
Thanks for your reply kimbert.
The broker is 6.0.0.4
The toolkit is 6.0.2 |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri May 22, 2009 7:54 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Are you planning on upgrading to v6.1 any time soon? If so, you should design your message flows so that they can take advantage of the v6.1 support for web services.
The MRM message set has a setting which allows you to control xsi:type. If that doesn't do what you need, then you will need to switch over to XMLNSC. On v6.0, XMLNSC cannot validate, but there are other options http://www.mqseries.net/phpBB2/viewtopic.php?t=49220 |
|
| Back to top |
|
|
| Risto |
| Posted: Fri May 22, 2009 11:04 am Post subject: |
|
|
Newbie
Joined: 29 Apr 2009
Posts: 6
|
| Thanks kimbert. I am at a customer site and I dont think they plan to upgrade anytime soon. I somehow fixed the problem. I say somehow becuase I made a lot of changes and eventually it work. I did make manual changes to my message set after importing the wsdl which I think resolved the problem. I guess I assumed the WSDL imported and created a good message set but it did not. |
|
| Back to top |
|
|
|
|
