Hello, I think this is because the JMS BC enable access to external queues.
To call external service you should use CXF BC. The EIP Pipeline convert InOnly into InOut and forward the result of the InOut to an InOnly target. Regards Vivian -----Message d'origine----- De : jcamus [mailto:[email protected]] Envoyé : jeudi 27 août 2009 08:43 À : [email protected] Objet : Re: How to process messages from a JMS provider into SMX? 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.
