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 » XML to TDS - Input Parsing

Post new topic  Reply to topic
 XML to TDS - Input Parsing « View previous topic :: View next topic » 
Author Message
IntegratorWMB
PostPosted: Thu Apr 24, 2008 7:16 pm    Post subject: XML to TDS - Input Parsing Reply with quote

Apprentice

Joined: 06 Dec 2007
Posts: 27

All,

I have a message flow which converts an incoming xml to tdf.

I designed the Message Domain as MRM. On the Input Message Parsing I used MRM even though the incoming message is xml. There will always be only one client for this message flow and the client code shares the same xsd with message broker . The xml contains CDATA section.

When I use MRM as the input parser :

the cdata section contains extra spaces

(0x0300000B):BodyContent = '
HEADER
----------
.......
'
)

whereas I don't see those extra spaces when I use the XMLNSC parser.
and the xmlnsc parser show PCDATA as part of the cdata section. Is this PCData section converts to extra spaces in MRM parser. If yes, how can I truncate those extra spaces?

(0x01000000):BodyContent = (
(0x02000000):PCDATA = '
'
(0x02000001):CDATA = ' HEADER
----------


(0x02000000):PCDATA = '
'
)
)

Since the input will always be xml, I think using xmlnsc parser is a better option even if the message domain is MRM and there is no input validation.

Will there be a performance issue using XMLNSC parser as the volume of messages are really high?

Thanks
Back to top
View user's profile Send private message
kimbert
PostPosted: Fri Apr 25, 2008 1:27 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
Will there be a performance issue using XMLNSC parser as the volume of messages are really high?
There certainly will, but it's a positive effect. Your CPU costs for XML parsing will drop by a factor of at least 4, probably more.
If you're on v6.1, you will be able to validate in the XMLNSC domain as well. If you're still on v6, you're well positioned to take advantage after you upgrade.
Back to top
View user's profile Send private message
IntegratorWMB
PostPosted: Fri Apr 25, 2008 5:40 am    Post subject: Reply with quote

Apprentice

Joined: 06 Dec 2007
Posts: 27

Do you know why MRM parser add those extra white spaces on CDataSection?

Thanks
Back to top
View user's profile Send private message
kimbert
PostPosted: Fri Apr 25, 2008 11:12 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Yes. Or to be more correct, I know why XMLNSC removes the whitespace. Go to the Parser Options properties page on the input node. In the XMLNSC properties, you will find a property 'Suppress mixed content'. Its default setting is to suppress mixed content.
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 » XML to TDS - Input Parsing
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.