MQSeries.net :: View topic - Difference in XMLNS and XMLNSC Parser

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Difference in XMLNS and XMLNSC Parser

Difference in XMLNS and XMLNSC Parser

« View previous topic :: View next topic »

Author

Message

EricCox

Posted: Wed Apr 01, 2015 7:14 am Post subject: Difference in XMLNS and XMLNSC Parser

Master

Joined: 08 Apr 2011
Posts: 292

To all,

Has there been a change in behavior between the XMLNS and XMLNSC Parser in regards to how it identifies the existence of the XML Declaration?

When using XMLNS Parser we had this code working where it would produce a TRUE result while reaching for the Original Request.

IF InputRoot.ComIbmAggregateReplyBody.IWDCustInqRq.XML

Now when switching to XMLNSC the parsers says it can't navigate to the Fourth element as such:
Failed to navigate to path element number '4' because it does not exist.

Can someone help me understand why XMLNSC Parser does not find the XML declaration with this XPath?

Thanks much to all,
Eric

kimbert

Posted: Wed Apr 01, 2015 8:11 am Post subject:

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:

Has there been a change in behavior between the XMLNS and XMLNSC Parser

They are different parsers. XMLNSC is not a plug-in replacement for XMLNS.

Quote:

in regards to how it identifies the existence of the XML Declaration?

The parser does not 'identify the existence' of anything. The parser creates the message tree. ESQL allows you to query and manipulate the message tree. XMLNSC and XMLNS create different message tree structures.

Quote:

When using XMLNS Parser we had this code working where it would produce a TRUE result while reaching for the Original Request.

IF InputRoot.ComIbmAggregateReplyBody.IWDCustInqRq.XML

Now when switching to XMLNSC the parsers says it can't navigate to the Fourth element as such:
Failed to navigate to path element number '4' because it does not exist.

Good idea to take a user trace. The next step is to put a Trace node into the message flow, set the pattern to ${Root} and allow it to write its output into the User Trace. Then you will quickly see the difference between the tree structure created by XMLNS and the tree structure created by XMLNSC.

Quote:

Can someone help me understand why XMLNSC Parser does not find the XML declaration with this XPath?

Yes. You can, using standard message flow debugging techniques. Or by reading the Knowledge Center topics on XMLNSC.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Difference in XMLNS and 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