| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Difference b/w XMLNS and XMLNSC parser. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Fri Aug 21, 2009 6:44 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Jimmy3 wrote: |
| some cases I have seen parser complains to work with a well formed message, that has namespace. Not sure of this reason though, but switching back to XMLNS makes it work! |
There is (or should be) no difference between how the 2 parsers build a message tree from a namespaced XML document. The only difference is that XMLNSC doesn't include whitespace in the message tree. If you know different, and have evidence, it's PMR time.
| Jimmy3 wrote: |
| So we need all of them currently, and future years to come. |
You don't need XML. It's depreciated.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Aug 21, 2009 6:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Mut1ey wrote: |
| Quote: |
| Tip: If you require message tree to conform as closely as possible to the XML data model, perhaps because you are using certain XPath expressions to access the message tree, use the XMLNS domain. |
I would say that the above is one reason why you would use XMLNS over XMLNSC. |
I'd rewrite the XPath correctly to not rely on whitespace elements.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
