Well, not quit sure I follow you there about other software  and still
think it is not a good idea to copy those specific headers.

Most likely the WMQ protocol are creating new values for those headers when
the message is actually put on the queue. I am not sure you can actually
change that.

You could try to create a Processor class which basically hard codes the
destination headers one by one with values from source and see if that
helps.

Alternatively, copy those headers into the MQRFH2 header which is usually
not changed by WMQ. It is used when you want to include meta-information
about the message. So you can create a new structure in MQRFH2 called
sourceMQMD and copy all the source headers in there and this can be then
viewed when you want to know the source MQMD headers.

On Fri, Jul 22, 2016 at 1:11 PM, mjok [via Camel] <
[email protected]> wrote:

> Well, it's an legacy system, I might have a problem with other software
> witch is using messages from destination queue.
> Besides it's in requirements..
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/WMQ-message-context-tp5785336p5785358.html
> To start a new topic under Camel - Users, email
> [email protected]
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/WMQ-message-context-tp5785336p5785359.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to