|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
CDATA setting |
« View previous topic :: View next topic » |
Author |
Message
|
rajbuddha |
Posted: Sun May 06, 2012 9:36 pm Post subject: CDATA setting |
|
|
 Apprentice
Joined: 02 Aug 2011 Posts: 47 Location: chennai
|
Hi Folks ,
Need your assistance . As per my requirment i need to set CDATA into two different tags , First one is wrapping xml into one tag , which i am doing as mentioned below
-----------------------------------------------------------------------
DECLARE wholeMsgBlob BLOB ASBITSTREAM(OutputRoot.XMLNSC,InputRoot.Properties.Encoding,InputRoot.Properties.CodedCharSetId );
DECLARE wholeMsgChar CHAR CAST(wholeMsgBlob AS CHAR CCSID InputRoot.Properties.CodedCharSetId);
SET soapBodyOutRef.ibm:login.(XMLNSC.CDataField)document1 = wholeMsgChar;
----------------------------------------------------------------------
And this is working as expected , But for the second tag CDATA i need to hardcode some xml content , for this i am following syntax mentioned below
--------
SET soapBodyOutRef.ibm:login.(XMLNSC.CDataField)env = '<YFSEnvironment userId="admin" ProgId="testWS" />' ;
----------
and this giving me the result like
---------
<env><YFSEnvironment userId="admin" ProgId="testWS" /></env>
-----------
But i am expecting like
---------
<env><![CDATA[YFSEnvironment userId="admin" ProgId="testWS" />]/env>
----------
Please help me with this ...Thanks in advance _________________ -----------
Raju Buddha
Never Wait for your 2nd Opportunity..!Becoz it may be harder than the 1st One... |
|
Back to top |
|
 |
kash3338 |
Posted: Mon May 07, 2012 8:00 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
|
Back to top |
|
 |
kimbert |
Posted: Mon May 07, 2012 1:02 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
And this is working as expected , But for the second tag CDATA i need to hardcode some xml content , for this i am following syntax mentioned below |
Well...if it works in the first part of the message then it should work in the other part too. XMLNSC works the same way on all parts of the the message tree.
My best guess is that you have made a simple typing error somewhere - the best way to find that is to put in a Trace node and look at the contents of the message tree just before the output node. |
|
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
|
|
|
|