senthil.arumugam wrote:
Hi Willem,
Our use case is, we need to save or update the entity.
For eg,
We have a message of instance Foo and we need to decide whether the instance
to be saved or updated etc. This behavior is common across all the messages.
So we are wrapping Foo (actual message en
Hi Willem,
I am using Camel 2.4.0 and let me try the same with 2.5-SNAPSHOT as you
mentioned and update the same once I am done.
Thanks,
- SK
--
View this message in context:
http://camel.465427.n5.nabble.com/Add-header-for-each-message-tp2651224p2797607.html
Sent from the Camel - Users mailin
Hi Willem,
Our use case is, we need to save or update the entity.
For eg,
We have a message of instance Foo and we need to decide whether the instance
to be saved or updated etc. This behavior is common across all the messages.
So we are wrapping Foo (actual message entity) with SampleMessage
senthil.arumugam wrote:
Hi Willem,
I thank you for your reply. That was a way we were thinking, using which we
can differentiate various messages and route them as needed.
Now we have achieved it by wrapping the actual message with another object
of type Message which use generics to return the
Hi Willem,
I thank you for your reply. That was a way we were thinking, using which we
can differentiate various messages and route them as needed.
Now we have achieved it by wrapping the actual message with another object
of type Message which use generics to return the entity and holds a value
Hi,
I wrote some test to implements your request and found current Proxy way
can't not inject the header as you want, because Camel will create a
BeanInvocation to hold the invocation information of the dynamical
proxy. It is hard to tell the route to filter the header from you message.
If y