| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB Parsing - Message Tree and Logical tree |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqxplorer |
 Posted: Tue Nov 01, 2011 7:41 am Post subject: WMB Parsing - Message Tree and Logical tree |
 |
|
Master
Joined: 22 Jun 2009
Posts: 206
|
May be I am asking some basic question but I am bit confused with the "PARSING" explanation in one of the documents I was reading and some info from Info center.
Is the LOGICAL tree structure we see in DEBUG mode different from the Message tree created when the message is parsed by the input node?
May be this sounds ridiculous but the reasons I got this question was ....
By default when the message comes on to the input node, the message body is not parsed imemdiately, it will be prased on 'On Demand' basis, that means the message body will be parsed based on the message fileds reference in the flow. This means the message tree creation by the node is to the extent where the elements are referenced. However, when we see in the debug mode, we can see the whole message in the logical tree structure. This made me confused with the terms "LOGICAL TREE" and "MESSAGE TREE".
May be I am not getting it at all...
Could someone help me understand this bit more in detail? It would be really a great help.
Thanks in advance
Thanks
mqxplorer |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Nov 01, 2011 8:02 am Post subject: Re: WMB Parsing - Message Tree and Logical tree |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqxplorer wrote: |
| Could someone help me understand this bit more in detail? It would be really a great help. |
If you've got the debugger switched on, then the "On Demand" parsing is performed when the debugger demands that it, i.e. when the debugger decides it wants to display the message tree to you. So the full message tree is produced for the benefit of the debugger.
And yes, this does mean that the message tree is parsed at a different time and in a different way with the debugger in use. Because with the debugger switched off, the tree is only parsed as the fields are referenced.
This is why the advice to solve parsing problems is to take a user trace. So you can see how the tree is being parsed as the fields are referenced.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqxplorer |
| Posted: Tue Nov 01, 2011 8:20 am Post subject: |
|
|
Master
Joined: 22 Jun 2009
Posts: 206
|
Hi Vitor,
Thanks a lot for your repsone and great explanation. I have been reading a lot of documents and was kind of lost. I feel very relaxed now.
This forum makes my life easy everytime when I am in a trouble.
Thanks
mqxplorer |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Nov 01, 2011 8:52 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| And yes, this does mean that the message tree is parsed at a different time and in a different way with the debugger in use. |
At least, it *used* to. Since v7 the debugger uses its own copy of the parser, and leaves the message flow's copy alone, which is a big improvement. So the debugger should not change the behaviour of your message flows these days...
Before others jump in and say it...that doesn't mean that Trace nodes and user trace are not essential debugging tools. It just means that the debugger works a lot better than it used to. |
|
| 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
|
|
|
|
