| Author |
Message
|
| pcelari |
 Posted: Wed Sep 17, 2008 1:10 pm Post subject: anyone has ever had XML.AsisElementContent working? |
 |
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
Hi,
I need to prevent reserved XML characters contained in my message from being converted. So following the document I used the XML.AsisElementContent. But it doens't work, creating an output with the content totally cut off, i.e. empty.
I wonder if anyone out there has ever successfully used the feature.
thanks for sharing your knowledge.
Manual:
Set OutputRoot.XML.(XML.Element)Message.(XML.AsisElementContent) = '<rawMarkup>';
generates the following output message:
<Message><rawMarkup></Message>
This shows that the value of an AsisElementContent syntax element is not modified before it is written to the output message.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Sep 17, 2008 1:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you tried CData ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pcelari |
| Posted: Wed Sep 17, 2008 1:22 pm Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
No. do you happen to have an example how to use it. the section in the manual doesn't tell how to use it in a set statement.
XML CDataSection
CData sections in the XML message are represented by the CDataSection value element. The content of the CDataSection element is the value of the CDataSection element without the <![CDATA[ that marks its beginning and the ]]> that marks its end.
For example, the following Cdata section:
<![CDATA[<greeting>Hello, world!</greeting>]]>
is represented by a CDataSection element with a string value of:
"<greeting>Hello, world!</greeting>"
Unlike Content, occurrences of <,>, &, ", and ' are not translated to their escape sequences when the CDataSection is written out to a serialized message (bit stream).
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 17, 2008 1:29 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Have you tried using a supported XML domain instead of the deprected OutputRoot.XML domain?
 |
|
| Back to top |
|
|
| pcelari |
| Posted: Wed Sep 17, 2008 1:55 pm Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
You meant XMLNSC? No, I'll do that in the future. at present level, we only use XML
Will it be easier to do what I need in XMLNSC?
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 17, 2008 2:01 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You shouldn't be using XML domain unless you are MQSI 2.1.
You should, at a *minimum* be using XMLNS.
If you are on WMB 6 or 6.1 you should be using XMLNSC for everything, regardless of whether you have namespaces or not. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Sep 17, 2008 2:57 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| mqjeff is correct. The XML domain is deprecated, and you should not be using it in new message flows. XMLNS is identical if you are not using namespaces. XMLNSC is the strategic choice ( and it supports XMLNSC.AsisElementContent ). |
|
| Back to top |
|
|
| pcelari |
| Posted: Thu Sep 18, 2008 3:56 am Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
thanks for the insight.
But a search in the infoCenter for XMLNSC.AsisElementContent yields nothing.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
|
|
