| Author |
Message
|
| Decky |
 Posted: Wed Dec 07, 2005 8:48 am Post subject: Tagged delimited Output problem |
 |
|
Novice
Joined: 16 May 2005
Posts: 16
Location: London UK
|
Hi,
I'm trying to create an output message in the following format
Tag:data:Tag1:data1: ... etc
where basically the tag-data separator is the same as the delimiter
I have created a compund type set to 'Tag Delimited' with the delimiter set to ':' and the tag data separator set to ':' as well . I get the following error
ParserException BIP5453E: Incoming message is self defining.
The message requiring writing is self-defining. TDS cannot write self-defining messages.
Anyone any ideas? I've tried following the manuals but obviously am doing something wrong. All my child elements have the tag property filled btw.
Cheers,
Dec |
|
| Back to top |
|
 |
| wooda |
| Posted: Wed Dec 07, 2005 9:18 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
This relates to the message tree which you are trying to write in TDS.
It contains self-defined elements.
ie. elements which do not appear in your message set.
This is fine in XML which is a self defining format.
But TDS cannot write a field you have not modelled as it does not have enough information to do so.
I assume you did not intend this, so something has gone wrong with creating your message tree.
How did you create the message tree ?
Trace the message tree and have a look at it, ths may help you see whats wrong with it. |
|
| Back to top |
|
|
| Decky |
| Posted: Wed Dec 07, 2005 9:21 am Post subject: |
|
|
Novice
Joined: 16 May 2005
Posts: 16
Location: London UK
|
| Strange because I did trace the tree, but I created it with a mapping node so I assumed all the correct elements would be there by default as I'd mapped them all. Will look into it in more detail |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 07, 2005 9:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Check that they are in the right order.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Dec 08, 2005 1:44 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| The message is pretty accurate, actually. It is saying that the entire message ( not just some of its fields ) is self-defining. In other words, the MessageType property does not match any of the messages in the message set. I suggest that you check that your MessageSet and MessageType properties are correct at the point where you attempt to write the message. |
|
| Back to top |
|
|
| Decky |
| Posted: Thu Dec 08, 2005 3:30 am Post subject: |
|
|
Novice
Joined: 16 May 2005
Posts: 16
Location: London UK
|
| All elements are in order and are mapped accordingly. One issue may be that the mapping node outputs the data in a comma separated format as there are two TDS layers (TDS_CSV for input, TDS_TAG for output). The mapping nodes picks TDS_CSV first by default by the looks of it. After the mapping node I have a compute node which changes the format to TDS_TAG (an RCD didn't work for some reason) |
|
| Back to top |
|
|
| Decky |
| Posted: Thu Dec 08, 2005 3:42 am Post subject: |
|
|
Novice
Joined: 16 May 2005
Posts: 16
Location: London UK
|
| just realised you can set the format in the mapping node |
|
| Back to top |
|
|
| Decky |
| Posted: Thu Dec 08, 2005 4:00 am Post subject: |
|
|
Novice
Joined: 16 May 2005
Posts: 16
Location: London UK
|
 Fixed!! dumped the compute node and set the TDS_TAG in the mapping node. Thanks guys for pointing me in the right direction |
|
| Back to top |
|
|
|
|
