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.
