| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Prefix in XML output using XML wire format |
« View previous topic :: View next topic » |
| Author |
Message
|
| jakob |
 Posted: Wed Jul 14, 2004 4:54 am Post subject: Prefix in XML output using XML wire format |
 |
|
Newbie
Joined: 07 Jul 2004
Posts: 4
|
Hi,
I have a problem with generating XML output from a WBI broker version 5. I am sending to a SAP adaptor. The message set is generated from XSD files. F.x. MATMAS05 is generated from 25+ files. One is called sap_iddoccontrol.xsd. An element is called Client.
The adaptor expect the XML name to have a prefix with the name of the XSD file it is generated from. This means a Client should be
<sap_idoccontrol:Client>jakob</sap_idoccontrol:Client>
The WBI 50 output is
<Client>jakob</Client>
The old version 21 made the correct output
<sap_idoccontrol:Client>jakob</sap_idoccontrol:Client>
When importing the XSD files to version 21 made the XML name for Client
'sap_idoccontrol:Client'
When importing to version 50 the XMLname is just 'Client'
Please help 
Thanks
Jakob |
|
| Back to top |
|
 |
| alexey |
| Posted: Wed Jul 14, 2004 7:06 am Post subject: |
|
|
Acolyte
Joined: 18 Dec 2003
Posts: 62
Location: Israel
|
Check if the message set has "use namespaces" enabled and the wire format includes all the prefixes of the namespaces from the XSDs. If no - enable namespaces, set default wire format and import your XSDs again.
Alexey. |
|
| Back to top |
|
|
| shanson |
| Posted: Fri Jul 16, 2004 5:35 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
Be careful here. In 2.1 XML namespaces were not supported by the XML or MRM parsers, so the workaround was to use the MRM domain XML physical format 'XML Name' property to include both prefix and name. This technique was used by the 2.1 XML Schema importer.
This mode of working is supported in V5 by NOT selecting the 'Use Namespaces' check box on the message set. If you re-import the schema the intention is that it should behave like 2.1, so 'XML Name' should be set. If it is not then raise a PMR.
If you want to move to handling namespaces 'correctly', you can use a message set with 'Use Namespaces' checked. But if you do this, and your schema uses namespaces, a) you can not deploy to a 2.1 broker; b) your ESQL will be different as it will have to contain namespaces in paths; c) any ESQL you wrote for 2.1 will not work. |
|
| 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
|
|
|
|
