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 » Cdata Parsing issue

Post new topic  Reply to topic Goto page Previous  1, 2
 Cdata Parsing issue « View previous topic :: View next topic » 
Author Message
timber
PostPosted: Tue Jul 19, 2016 4:49 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

Please try this:
- Create an input XML message that contains multiple CDATA sections within the same tag
- Call FIELDVALUE on the *parent* tag ( the tag that contains all of the CDATA sections)
What result do you get?

btw, this has exactly *nothing* to do with
- XML schema
- validation
- DTDs
Back to top
View user's profile Send private message
shwetabh WMB
PostPosted: Tue Jul 19, 2016 5:20 am    Post subject: Reply with quote

Novice

Joined: 15 Jul 2016
Posts: 23

Thanks.
Yes it should not be issue with DTD as it can take reference from http://xyz.com .
However,below happens after parsing .(changed data a bit)
' (CHARACTER)
(0x01000000:Folder )http://xyz.com:abc = (
(0x02000001:CDataValue):CDATA = '[[Indiasddff' (CHARACTER)
(0x02000001:CDataValue):CDATA = '] is 4-8 xyzsed; [Mrtyeabc' (CHARACTER)
(0x02000001:CDataValue):CDATA = ']straight sell' (CHARACTER)
(0x02000001:CDataValue):CDATA = ']' (CHARACTER)
)
(0x02000000:PCDataValue):PCDATA

FIELDVALUE() gives the consolidated value .However,SET OutputRoot.XMLNSC.....=InputRoot.XMLNSC..... gives ROW.
"The result was ''ROW... Root Element "
This is quite obvious as SET will assign the target type same as source type which is ROW.
Back to top
View user's profile Send private message
timber
PostPosted: Tue Jul 19, 2016 5:29 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

You are over-thinking this. You need to get all of the text content of the tag as a single string, regardless of how many CDATA sections there are. You now have a way to do that.

The XMLNSC parser has good reasons for splitting CDATA sections. If you open a PMR then IBM will tell you exactly when the splitting will happen. However, I'm not sure that the information would do you much good; it is already pretty obvious that your message flow needs to cope with the possibility of multiple CDATA sections.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Jul 19, 2016 5:30 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Ok.

That firmly sounds like a problem with the input message.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
shwetabh WMB
PostPosted: Tue Jul 19, 2016 5:43 am    Post subject: Reply with quote

Novice

Joined: 15 Jul 2016
Posts: 23

Thanks:)

Yes we do have resolution.I stated that before.We wanted to know the reason of such splitting.
Waiting for IBM to reply .
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Cdata Parsing issue
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.