| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| HTTP Reply, bitstream, Message set |
« View previous topic :: View next topic » |
| Author |
Message
|
| fazz |
 Posted: Wed May 10, 2006 2:48 am Post subject: HTTP Reply, bitstream, Message set |
 |
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
Hello,
I have a flow that receives an input via HTTP, writes the message to a queue then responds back to the calling web service using the HTTP Reply node.
This all works fine.
I construct a reply, and pass it to the HTTP Reply node, I would like to parse this reply against a message set.
So I set the OutputRoot.Properties message set values, thinking that when the HTTP Reply nodes recieves the message it will create a bitstream and parse it against the message set.
However, if I create an invalid message, the HTTP Reply node happily sends the response to the calling client,seemingly not parsing the message against the message set.
Is this normal behaviour?
Can the HTTP Reply node parse messages when creating a bitstream?
Cheers |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed May 10, 2006 4:27 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi fazz,
| Quote: |
| I set the OutputRoot.Properties message set values, thinking that when the HTTP Reply nodes recieves the message it will create a bitstream and parse it against the message set. |
I'm a bit puzzled. The HTTPReply node is an output node, so it does not do parsing. What is your requirement? Do you simply want an error to be issued if the message is invalid? |
|
| Back to top |
|
|
| fazz |
| Posted: Wed May 10, 2006 4:33 am Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
Hi Kimbert
I was under the impression that an output node would create a bitstream of a message it received and if the properties folder contained details about a message set then it would parse the message against it.
Am I way of the mark?
Cheers |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed May 10, 2006 6:13 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Am I way of the mark? |
You're close, but not close enough 
An input node ( or perhaps some other node downstream of it, if Parse Timing is set to 'On Demand') will create a message tree from a bitstream. That's parsing.
An output node will send a bitstream to MQ, or over http or some other transport. In order to obtain the bitstream, it may need to convert a message tree to a bitstream. That's serialization or writing.
If an output node is given a bitstream, it will use it as-is. If you want your message to be parsed before it leaves your message flow ( for whatever reason) then you'll have to put logic into your message flow to do that ( RCD node or ESQL ). |
|
| Back to top |
|
|
| fazz |
| Posted: Wed May 10, 2006 6:18 am Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
...and all becomes clear....
thanks kimbert, that makes sense, I was confusing serialization with parsing.
many thanks |
|
| 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
|
|
|
|
