The source code for InOut over JMS is all in the camel-jms component.
Mind there is a lighter alternative component called camel-sjms, but
its not as battle tested or feature rich as camel-jms (which uses
spring jms).
On Fri, Feb 13, 2015 at 10:56 AM, Marco Crivellaro
wrote:
> Thanks for the rep
Thanks for the replies
Camel is only used to consume the request queue and post the replies, the
requestor is a .NET app based on NMS and the aggregation part works fine as
the setup works fine when using a standard queue on JMSReplyTo header: camel
is sending the multiple replies to the queue and
On Thu, Feb 12, 2015 at 6:11 PM, James Green wrote:
> I'm guessing you need the reply to include a reference to one or more
> "files" that can be picked up independently? I can't see a multi-message
> reply working. Prepared to be corrected of course.
>
Correct request/reply with Camel is a 1:1 m
I'm guessing you need the reply to include a reference to one or more
"files" that can be picked up independently? I can't see a multi-message
reply working. Prepared to be corrected of course.
On 12 February 2015 at 16:58, Marco Crivellaro
wrote:
> Hi,
> I have managed to get a simple request-r
