| Author |
Message
|
| Robert |
 Posted: Mon Mar 08, 2004 2:44 pm Post subject: WBI MB5 TDS Repeating problem |
 |
|
Apprentice
Joined: 22 Aug 2002
Posts: 46
Location: Quebec, Canada
|
Hi,
I'm trying to parse an MRM TDS Message with repeating elements.
In an attempt to keep things simple, I tried an example from a previous post that was developed with WMQI2.1 but cannot get it to work with V5.
I'm trying to parse the following message:
~Field1|Field2|Field3~Field21|Field22|Field23~
In the workbench, I did the following:
- Created a Complex Type: msgGroupType, Group Indicator ~, Group terminator ~ and delimiter |, All Elements Delimited. Added 3 elements Field1, Field2 and Field3 of type String to msgGroupType.
- Created a Global Element named msgGroup of group type msgGroupType.
- Added a new message named msgGroup from Global Element msgGroup.
- Created a simple message flow to test the message set.
Added a trace Node just after MQInput.
- Inserted the test message and got the following error when attempting to parse the message.
"MRM parsing error. message bit stream larger than expected.
The bit stream of the message being parsed by the MRM is larger than expected for a message of this message type...."
The message is parsed correctly if I MQPUT the following message:
~Field1|Field2|Field3~
It seems that I cannot get the parser to read more than one instance of a group.
Any help or guideline on how to tackle this problem with V5 will be appreciated.
Thanks.
Robert |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Mar 08, 2004 2:57 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't think you want to create a message of your msgGroupType.
I think you want to create a message that contains an element of your msgGroupType.
Then set the repeating properties on this element, to indicate that the message itself contains multiple instances of the element.
You may need to adjust your group terminators and indicators to prevent the parser from expecting ~(groupElements)~~(groupElements)~.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Robert |
| Posted: Tue Mar 09, 2004 5:13 am Post subject: |
|
|
Apprentice
Joined: 22 Aug 2002
Posts: 46
Location: Quebec, Canada
|
Hi Jeff,
You are right, I want to create a message containing an element of msgGroupType.
I modified the message layout to reflect this. The parser still cannot "digest" the message with repeating occurences of the element. Still have the "Bitstream too big..." message in the NT Event Log.
When you mention the "repeating properties", do you refer to the MaxOccurences count? The delimiter for repeating fields? I noticed that in the WMQI V2.1 documentation that they refer to a property named "Repeat" where you can set the value to "Yes".
I can't find it in V5. Maybe the MaxOccurence greater than one implies Repeat = "Yes"...
I surely miss a small detail somewhere but cannot pinpoint it. Any other clues?
Thanks for your help
Robert |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 09, 2004 7:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| WBIMB Help system wrote: |
Cardinality: optional, repeating and mandatory elements
Elements
The number of occurrences of an element can be controlled using the properties minOccurs and maxOccurs. Using these properties, an element can be defined as mandatory, optional or repeating.
A mandatory element has minOccurs >= 1. A mandatory element must must occur at least once in an input message.
An optional element has minOccurs = 0. An optional element can be omitted from the input message.
A repeating element normally has maxOccurs > 1. It can occur more than once in the input message, and all the occurrences must appear together without any other elements between them.
|
So, yeah, it's the minOccurs and maxOccurs on the Local Element page under Logical Properties.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Robert |
| Posted: Tue Mar 09, 2004 7:20 am Post subject: |
|
|
Apprentice
Joined: 22 Aug 2002
Posts: 46
Location: Quebec, Canada
|
Thanks Jeff,
I already read this part of the documentation. I was just wondering if I was missing anything since all the information I am gathering these days pertaining message sets is an hybrid of WMQI 2.1 and MB V5.
Robert |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 09, 2004 8:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Robert wrote: |
| I was just wondering if I was missing anything |
I don't think so.
Bitstream too big just means that you don't have things set correctly, or at least your message doesn't match the way you have it set...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Mar 11, 2004 4:55 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Have you tried removing the group terminator? The way you have designed the message model, you will get this:
| Quote: |
| ~(groupElements)~~(groupElements)~ |
as already stated by Jeff. |
|
| Back to top |
|
|
|
|
