you need to think of each jms message as a fire and forget entity,
immutable once sent. The properties whose name begin with "JMS" are
for use by the JMS implementation so they will be set by the sender
JMS implementation code to what ever is needed by the implementation.
An application is in cont
Hmm, this is interesting.
If I set in a new JMS message the destination Queue to "aaa" with the
method setJMSDestination() but sent the JMS Msg to another queue "bbb" then
the JMS header field JMSdestination will will be brutally overwritten with
"bbb".
I can imagine that this happens with the
It will be a new message with a new Id, so you will need to explicitly
set the correlationID to the original messageID
On 13 August 2010 14:28, Martin C. wrote:
> Hi,
>
> On Fri, Aug 13, 2010 at 2:30 PM, Gary Tully wrote:
>>
>> you need a message producer and do producer.send(..., message);
>>
>
Hi,
On Fri, Aug 13, 2010 at 2:30 PM, Gary Tully wrote:
>
> you need a message producer and do producer.send(..., message);
>
will this also preserve the message ID or will a new message ID be
used for this message? I am interested as I may need to forward some
messages to another broker and I'd
you need a message producer and do producer.send(..., message);
On 13 August 2010 12:40, BenXS wrote:
>
> Assume I wrote a Java bean (configured by Spring) which receives successfully
> incoming messages on a certain queue. So the "onMessage()" method looks
> similar like:
>
> public void onMessa
Assume I wrote a Java bean (configured by Spring) which receives successfully
incoming messages on a certain queue. So the "onMessage()" method looks
similar like:
public void onMessage(Message message) {
...
}
Now I want to forward/sent the just received message into another queue
"bbb
