| Author |
Message
|
| PieterV |
 Posted: Mon Mar 26, 2007 11:07 pm Post subject: Validition Node: Set properties trough ESQL |
 |
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
Case: message format with different types of messages.
Input node takes the message of a queue, but does not perform a validation. The format is XMLNS.
Based on a field in the XMLNS (root tag), we would like to decide wich type of message it is and then in the next node perform the validation of that type of message.
(I probably have to set a resetcontentdescripter after the input node)
Message Set and Message Format stay fixed, but the Message Type is variable.
How can i influence to value of Message Type to be checked in a validation node (or resetcontentdescriptor node) by ESQL? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Mar 27, 2007 3:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Message validation is only available with MRM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PieterV |
| Posted: Tue Mar 27, 2007 4:48 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
Indeed,
but when you use XML and MRM you loose the root tag for some reason.
In our message(s) the roottag contains the type of message. So in the input node the message is XMLNS format. We take the roottag and then we want to use the value in the roottag to put in the Message Type property in the resetcontentdesciptor (and make a MRM message from it to validate).
The mxsd will contain multiply messages, so multiple types. Given the roottag of the xml message we want to decide wich type op message it is. and then map the message on the mxsd. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 27, 2007 9:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, if you're changing from XMLNS to MRM, then the Message Set and Message Type properties aren't fixed.
But you can just Set OutputRoot.Properties to accomplish the same things that a ResetContentDescriptor node does.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Mar 27, 2007 11:24 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| FYI, you are not getting any extra validation by doing it this way. If you leave the message type empty then the MRM XML parser will automatically select the message definition which matches the root tag. |
|
| Back to top |
|
|
| PieterV |
| Posted: Tue Mar 27, 2007 9:59 pm Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
kimbert,
that's interesting.
So we can make a message set, with multiple messages in it .
And then put that message set in the properties of the input node and it will automaticly chose its corresponding type? (and do the validation?) |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Mar 28, 2007 12:29 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
| Back to top |
|
|
| PieterV |
| Posted: Wed Mar 28, 2007 1:31 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
My admiration for this product growes every day 
thanks Kimbert. |
|
| Back to top |
|
|
|
|
