| Author |
Message
|
| cadenza |
 Posted: Tue Jul 05, 2005 3:08 am Post subject: Setting encoding in XML declaration |
 |
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi,
I want to set the following xml declaration using WMQI 2.1 control center.
<?xml version="1.0" encoding="UTF-16" standalone="no"?>
I am currently getting
<?xml version="1.0" standalone="no"?>
Thanks in advance. |
|
| Back to top |
|
 |
| RocknRambo |
| Posted: Tue Jul 05, 2005 5:52 am Post subject: |
|
|
Partisan
Joined: 24 Sep 2003
Posts: 355
|
What ESQL did u write for this...
try this
| Code: |
| OutputRoot.XML.(XML.XmlDecl).(XML."Encoding") = 'UTF-16' |
-RR |
|
| Back to top |
|
|
| cadenza |
| Posted: Tue Jul 05, 2005 8:21 pm Post subject: |
|
|
Apprentice
Joined: 01 Jun 2004
Posts: 48
|
Hi Rock,
Thanks for your reply.
Our message domain is MRM and so we have used the following code:
| Code: |
SET OutputRoot.MRM.(XML.XmlDecl) = '';
SET OutputRoot.MRM.(XML.XmlDecl).(XML."Version") = '1.0';
SET OutputRoot.MRM.(XML.XmlDecl).(XML."Encoding") = 'UTF-16';
SET OutputRoot.MRM.(XML.XmlDecl).(XML."Standalone") = 'no';
|
However the messages are failing. The trace log shows the following error:
ParserException BIP5502E: An Common Parser Interface internal error occurred: Diagnostic information: Empty tag name when creating a SearchDef object.
An internal error occurred while reading from or writing to the bitstream.
Please contact your IBM support center.
Im not sure if I need to make some changes to the message set XML wire format values |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Jul 05, 2005 10:36 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| Please contact your IBM support center. |
That sounds a little more serious than a mis-constructed XML Declaration. I would suggest a search of IBM's website, and if that doesn't turn anything up, a call to them.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Tue Jan 17, 2006 7:13 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
I have the same error with V5.0.6.
Anyone a hint how to add XML declaration to a MRM XML message?
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jan 17, 2006 9:02 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I searched for 'encoding MRM' and found this: http://www.mqseries.net/phpBB2/viewtopic.php?t=20119
You should also be aware that the MRM parser does not make use of the XML.(XmlDecl.*) element types - which may explain ( though not excuse) the internal error which you are getting. Those types are used only by the XML domain (and XMLNS/XMLNSC in v5/v6). |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Jan 22, 2006 10:21 pm Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
Thanks,
In the mean time I know a bit more about the XML.Encoding.
Although XML(NS/C) has the possibility for creating the encoding it doesn't use it, neither does the MRM. This is conform the XML recommendation as an external encoding has preference. In the case of the broker the Root.MQMD.CodedCharSetId is the external encoding.
So every application receiving an XML message over MQ should look at the MQMD.CodedCharSetId of the message instead of the encoding in the XML text declaration.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
| shanson |
| Posted: Thu Jan 26, 2006 2:28 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| The ability to add the Encoding attribute to the xmldecl for an MRM XML output message was added in WMB V6. Also the ability to set the version to '1.1'. |
|
| Back to top |
|
|
|
|
