| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Mapping node errors in different build in MB 6.1.0.2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| karthik_ps |
 Posted: Wed Mar 21, 2012 1:13 am Post subject: Mapping node errors in different build in MB 6.1.0.2 |
 |
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
Hi ,
I have a created msgflow with mapping node. This was created in version Message Broker 6.1.0.v20071108_1112 . When i import the same code in another machine having version MB 6.1.100.v20080515_1211 , some getting some weird exceptions in the mapping node.
Mapping node contains two different message set. Source message set is XML. Target msgset is fixed format. However, if i delete all those mapping and tried to deploy. That time, i got another new error at the same mapping node. These are sample errors thrown at mapping node.
Target "Offset" is unexpected at the given location in "File"
Target "Relationship" is unexpected at the given location in "RelatesTo"
Any help is highly appreciated.
Regards,
Karthik |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Mar 21, 2012 4:40 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| When i import the same code in another machine having version MB 6.1.100.v20080515_1211 , some getting some weird exceptions in the mapping node. |
What exceptions? How can we help unless you tell us?
| Quote: |
| Mapping node contains two different message set. Source message set is XML. Target msgset is fixed format. |
Like many WMB users, you seem to be confusing mapping with parsing:
- Parsers create message trees from physical formats.
- Transformation create message trees from other message trees
- Parsers create physical formats from message trees
In general the Mapping node does not know or care about the physical format of the input or output messages. Same goes for a Compute, JavaCompute or PHP node. So the Mapping node never looks at the physical formats in the message sets - it only cares about the logical structure.
| Quote: |
if i delete all those mapping and tried to deploy. That time, i got another new error at the same mapping node. These are sample errors thrown at mapping node.
Target "Offset" is unexpected at the given location in "File"
Target "Relationship" is unexpected at the given location in "RelatesTo" |
So the deploy failed, right? These are deploy-time errors, not errors from the message flow. First thing I would check is the 'Build automatically' setting in your WMB toolkit because the toolkit usually detects errors like this and stops you from building the BAR file.
btw, I am assuming that it was safe to delete those mappings. I don't know, but you should  |
|
| 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
|
|
|
|
