I'm not entirely sure I understand your desired flow, but it seems like you could do this one of two ways. You could easily define the entire route in Camel and use the file and JMS components. Alternatively, you could use the servicemix-file endpoint to send to the Camel route, and then from the camel route back to servicemix and use the servicemix-jms provider endpoint to put the message on the queue.
If you need another peice that reads the messages and does processing, you use the servicemix-jms consumer endpoint and send it to a servicemix-bean endpoint or whatever suits you. Let me know if I misunderstood the question. Chris -- Chris Custine FUSESource :: http://fusesource.com My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Directory Server :: http://directory.apache.org On Wed, Aug 26, 2009 at 9:09 AM, jcamus <[email protected]> wrote: > > Hi, > I need to have the following architecture : > > FilePoller -> CamelRouting -> JMS Provider -> <XXX> > > The <XXX> is a component that will regularly get the messages into the JMS > queue and process them. > How to do that into SMX ? Must I have a Bean-SE component with dedicated > java code to manage that ? Or is a specific component already done for > that? > More generally, how into SMX is managed messages into a JMS queue? How can > we simply process messages into a SMX JMS queue? > > Thanks for your help. > > > -- > View this message in context: > http://www.nabble.com/How-to-process-messages-from-a-JMS-provider-into-SMX--tp25151415p25151415.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
