ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » CR|LF - XMLNSC Parser

Post new topic  Reply to topic
 CR|LF - XMLNSC Parser « View previous topic :: View next topic » 
Author Message
IntegratorWMB
PostPosted: Mon May 05, 2008 4:44 am    Post subject: CR|LF - XMLNSC Parser Reply with quote

Apprentice

Joined: 06 Dec 2007
Posts: 27

I have an incoming xml parsed by the XMLNSC Parser and the message gets transformed to a TDF and send to an output queue. If there are no issues the original message contains a CDATA section which has a status messsage that I need to send it to a status application thru mq.

The status message has CR | LF ( 0D & 0A ) as the line separators.

The status application receives the status message with 0A as the line separator and not with CR | LF. Is this an expected behavior?

I am using WMB 6.1

I had defined my Status message as TDF (ComplexType Seq) containing 1 (or) more Strings where each String is delimited by the CR | LF as delimiter. And In the Status compute node I assign it as follows

SET statusMessage = msg.Status.(XML.CDataSection);

where the incoming message has something like below:
<Status>
<!CDATA[[....
]]>
</Status>

Thanks for any pointers
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon May 05, 2008 4:57 am    Post subject: Re: CR|LF - XMLNSC Parser Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

IntegratorWMB wrote:
I have an incoming xml parsed by the XMLNSC Parser


Good.

IntegratorWMB wrote:
SET statusMessage = msg.Status.(XML.CDataSection);


This is not correct for the XMLNSC parser. It's only correct for the XMLNS parser.

Don't use the XMLNS parser, fix this statement so it's correct for the XMLNSC Parser.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
IntegratorWMB
PostPosted: Mon May 05, 2008 5:14 am    Post subject: Reply with quote

Apprentice

Joined: 06 Dec 2007
Posts: 27

Thanks for pointing jeff.

SET statusMessage = msg.Status.(XMLNSC.CDataValue);

Still I am seeing LF as the delimiter on the outgoing status message.
Back to top
View user's profile Send private message
kimbert
PostPosted: Mon May 05, 2008 9:43 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

You're experiencing line feed normalization, which is correct behaviour for all standards-compliant XML parsers.
http://www.w3.org/TR/2006/REC-xml-20060816/#sec-line-ends
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » CR|LF - XMLNSC Parser
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.