Posted: Wed Apr 21, 2004 2:39 am Post subject: which is a better implementation of message flows
Apprentice
Joined: 16 May 2002 Posts: 29 Location: chennai
hi guys
i have a generic xmlmessage on a queue.according to my requirent i need to use a compute node where some fields are removed and some new firleds are added.
there are 2ways to do this
1.use like a generic xm where the message is not defined
2.describe the message in mrm and try to do all the changes
plz advice me which is the best way for dealing with generic xml messages and which is very easy to implement
regards
srinivas
Joined: 25 Mar 2002 Posts: 184 Location: Purchase, New York
Personally, I never describe the XML message. I just reference the fields as needed. Not sure what value describing the XML message has (other than it forces you to really understand it), or to be able to drag/drop to create the ESQL (which I never use).
I'm interested to see 'pros' to defining the XML message...
The pros of defining the XML message in the MRM is to be able to validate the contents of the XML incoming data using the MRM, instead of having to write ESQL.
Using the MRM to parse and validate XML is slower than using the XML or XMLNS parsers. _________________ I am *not* the model of the modern major general.
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