| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| message set with unbound maxoccurs |
« View previous topic :: View next topic » |
| Author |
Message
|
| Karian |
 Posted: Thu Aug 17, 2006 12:41 am Post subject: message set with unbound maxoccurs |
 |
|
Newbie
Joined: 17 Aug 2006
Posts: 2
|
I'm having a little problem with a message set I'm using.
The message looks like this:
A;B;C;D;E
a;b;c;d;e
1;2;3;4;5
...
the message set just consist of a "row" element with max occurs unbounded (min 0 max -1) and contains a "field" element of type xsd:string that appears exactly 5 times (min 5 max 5).
When the message gets parsed like this, it just creates 1 row with in the last element all the rest of the message.
The strange thing is, is that if I put a certain number in the max occurs of the row-element, the message is parsed correctly.
Does anyone know what the problem can be? |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Thu Aug 17, 2006 1:26 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Karian,
Did you specify a delimiter for field as <CR><LF> ?
| Karian wrote: |
| When the message gets parsed like this, it just creates 1 row with in the last element all the rest of the message. |
This would mean that field is getting overwritten each time. 
Little more info plz...
| Karian wrote: |
| The strange thing is, is that if I put a certain number in the max occurs of the row-element, the message is parsed correctly. |
I think this is supposed to work so, else how would the parser differentiate the end of stream and a parser error ? What are the settings in your message set ? Can we have more details.
Regards. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Aug 17, 2006 4:39 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi Elvis,
- Which version/FixPack of message broker are you using?
- Your message is straightforward CSV ( but it uses ; instead of commas). Have you looked at the CSV samples provided with v6? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Aug 17, 2006 4:42 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Kimbert,
Can't answer those....its not my post.... 
Regards. |
|
| Back to top |
|
|
| Karian |
| Posted: Thu Aug 17, 2006 4:56 am Post subject: |
|
|
Newbie
Joined: 17 Aug 2006
Posts: 2
|
| elvis_gn wrote: |
Hi Karian,
Did you specify a delimiter for field as <CR><LF> ? |
Yes, that one is specified.
| elvis_gn wrote: |
This would mean that field is getting overwritten each time.
Little more info plz... |
It is not that the field is overwritten each time. With the example message sturcture above, a trace gives something like this:
(0x01000013):Row = (
(0x0300000B):Field = 'A'
(0x0300000B):Field = 'B'
(0x0300000B):Field = 'C'
(0x0300000B):Field = 'D'
(0x0300000B):Field = 'E
a;b;c;d;e
1;2;3;4;5'
)
The fact is that, with 999 as max number for row, the result does give multiple Rows (in the example 3) with each 5 Fields, split up correctly. I just can't understand why he can interpret that return correctly with a fixed max length, and not when it is unbounded.
I'm using version 5.0.7, and it is a migrated message set from 2.1 (didn't do the migration myself) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 17, 2006 5:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think if you build your model this way, it will work.
Message
* Body (min 0, max -1, group delimiter <CR><LF>)
** Field (min 5, max 5, delimiter 
But, as kimbert says - this is just a Comma-Separated-Values message with a ";" instead of a ",", and there are very good examples of this in the Samples Gallery installed on your machine.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
