| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| problem with CHOICE TYPE in CWF |
« View previous topic :: View next topic » |
| Author |
Message
|
| rajaram |
 Posted: Fri Jan 02, 2004 7:35 am Post subject: problem with CHOICE TYPE in CWF |
 |
|
Acolyte
Joined: 02 Jan 2004
Posts: 53
|
hi,
I have a small problem with CHOICE TYPE in CWF.
i have a compound type which is repeatable. It contains the following types.
1. header (length--1)
2. compound type--choice.
a) first record is of size 26
b) second record is of size 57.
I have read a topic in this forum which refers to the following site. It says if u have different lengths for records in choice type for CWF, we should then use multipart messages.
http://www.mqseries.net/phpBB2/viewtopic.php?t=8106&highlight=choice+cwf
Is there any other way on how i can handle this?
I have read in the manual that CHOICE cannot be resolved purely from data and that we have to handle that in the coding(ESQL).
In the input node, i feel i should mention domain as BLOB. right?
because, i will not able to parse the message and i feel that after the input node..i should write a compute node that handles this data. right?
I know this is a small one...but Please tell me how to handle this.
Thanks for any replies,
rajaram |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri Jan 02, 2004 9:12 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi,
Most of what you say is true:
- CWF cannot automatically resolve a choice based on the data in the bitstream. Instead, the CWF parser puts an unparsed section of the bitstream into the message tree. This section will be as large as a the largest element in the choice.
If your 26-byte record gets padded in the bitstream, then you're OK. Otherwise, the CWF parser will automatically consume 57 bytes for the choice, and will eat up the following records.
- You must resolve an unparsed node in ESQL. You just refer to whichever branch of the choice you want to use. The unparsed node will immediately be parsed based on the path which you specified.
I presume that the bitstream contains some kind of tag which identifies each record. It may be an idea to check whether you could use the TDS ohysical format to parse your message. |
|
| 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
|
|
|
|
