| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| problem with Mapping a target element from source msg elem |
« View previous topic :: View next topic » |
| Author |
Message
|
| hdjur |
 Posted: Thu Jan 11, 2007 5:39 am Post subject: problem with Mapping a target element from source msg elem |
 |
|
Centurion
Joined: 16 Sep 2004
Posts: 116
Location: Zagreb
|
Hi!
Message mapping editor states
in Source Pane:
$source - Properties, Headers, some_source_msg_name
in Target Pane:
$source - Properties, Headers, some_target_msg_name
When I define mapping with constant it's O.K.
When I reference source like this:
$source/some_source_msg_name/some_elem_name
there is no target element in the output MRM. The usual reason for this is ...? Thanks in advance. |
|
| Back to top |
|
 |
| hdjur |
| Posted: Thu Jan 11, 2007 7:07 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004
Posts: 116
Location: Zagreb
|
If source and target messages are the same, if I map like this:
$source/msg into $target/msg
all immediate children are properly mapped.
But this does not work (mapping children into children):
$source/msg/elem into $target/msg/elem
Mapping with constants does work.
Where did I possibly go wrong? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 11, 2007 7:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The most common cause for this is that the target expression actually evaulates to an empty field.
That is, "$source/msg/elem" resolves to an empty field.
Usually this is because the path is wrong, either because it's just typed wrong or because the namespaces are wrong.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Jan 11, 2007 10:06 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Are you using Message Sets? if so which type(XML,TDS..)? Did you see any warnings for particular elements while creating Message Definition files? |
|
| Back to top |
|
|
| hdjur |
| Posted: Tue Jan 23, 2007 1:09 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004
Posts: 116
Location: Zagreb
|
Thanks again pathipati and jefflowrey, for your consideration of my problem. Let me tell you that you were right. I was mapping multipart message, and didn't realize condition which was set to fn:false(), by default, for mapping particular inner message. When I changed it to something like this:
$source/outerMessage/messageIdentifier='msgAliasN'
for the Nth inner message mapping, I got what I wanted. Besides that, I did first mapping only for Nth inner message, and I was testing it for a while by putting Mth inner message, until I realized what I was doing. Of course that "$source/msg/elem" resolved to an empty field, in that case. |
|
| 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
|
|
|
|
