| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MRM - XML Domain Conversion Issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| upcominggeek |
 Posted: Tue Aug 29, 2006 9:40 am Post subject: MRM - XML Domain Conversion Issue |
 |
|
Apprentice
Joined: 21 Aug 2006
Posts: 35
Location: Boston, US
|
Due to the heavy restrictions in the message map conversion from v5-v6, I have decided to rather go for esql conversions completely ditching off message maps. First of all, if maps cannot handle indexed searching of elements, it is only half useful to me.
But the issue that I am facing is that when I say OutputRoot.XML.TOPELMT = InputRoot.MRM, interestingly, all the attributes of any element becomes an inner element. Not only that, my mixed elements (which has both attributes as well as value) becomes simple elements and the value of the mixed element is not mapped into the output xml. Anyone faced any issue like that? I am planning to convert the MRM to a BLOB and then to XML and see if that helps in anyway. But even if that works, I will still be surprised as to why a direct conversion doesn't work.
Any ideas appreciated. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 29, 2006 10:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Don't use OutputRoot.XML.
Use OutputRoot.XMLNSC.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| upcominggeek |
| Posted: Tue Aug 29, 2006 11:35 am Post subject: |
|
|
Apprentice
Joined: 21 Aug 2006
Posts: 35
Location: Boston, US
|
Nope. Same effect. Well, I am coding this in v5 and so I used XMLNS. But there is no difference in the output.
And converting from BLOB to XML using XML.AsisElementContent is not working either. Although it retains the tags, inside the node, it still treats the entire XML as a single string.
Not sure what to do now  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 29, 2006 1:57 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd say you need to post more code and trace information.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Aug 29, 2006 2:27 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I am planning to convert the MRM to a BLOB and then to XML and see if that helps in anyway. But even if that works, I will still be surprised as to why a direct conversion doesn't work |
That's the only approach which will preserve the attributes, but it will perform like something that doesn't perform very well.
Why? Because in a message tree built by an MRM parser, the nodes which represent attributes are no different from the other nodes. The MRM serializer only knows which nodes are attributes by doing a structured match-up of the names in the tree against the attributes/elements declared in the message set. This means that when an MRM tree is copied to an XML tree, it is almost impossible for the tree-copying process to know which of the nodes should be attributes ( I know that it is technically possible, but not many users actually want to copy MRM trees into trees owned by the other XML parsers.)
| Quote: |
| Any ideas appreciated. |
My first instinct is to say 'stay in the MRM domain'. Any reason why you particularly want to copy this MRM tree into an XML tree? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
