Re: How to process messages from a JMS provider into SMX?

[Gert Vanthienen <ge...@gmail.com>]

L.S.,

When the JMS or JCA flow are enabled, you'll get a queue per endpoint
indeed.  Whether or not these are persistent, needs to be configured
http://servicemix.apache.org/6-configuring-servicemix.html.  However,
using this approach, every MessageExchange will get
serialized/deserialized on every send.  If you want to ensure that
messages are being saved intermediately while processing, I would
personally recommend you to stick to your original approach with the
jms consumer/provider endpoint or add jms endpoints in your camel
route to get the same result, without the overhead of sending all
messages over JMS.  This will also get you ready for ServiceMix 4
where we no longer have the JMS flow.

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/8/27 jcamus <jc...@parkeon.com>:
>
> Thanks for this quick answer!
> By the way I just saw that SMX manages JMS internally for each endpoint
> defined. So why using JMS as a BC component into the SMX? it seems useless,
> isn'it? Maybe if I just used the following it should be ok :
>
> FilePoller -> Camel routing -> Transformation -> EIP Pipeline -> Bean Se to
> call external services
>
> Then this flow is asynchronous with the Pipeline and each message is kept
> until processed even if SMX is restarted? I am right?
>
> Regards.
>
>
> --
> View this message in context: http://www.nabble.com/How-to-process-messages-from-a-JMS-provider-into-SMX--tp25151415p25167070.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>