Re: FTP producer and exception or transaction

gt;            * <!-- This replaces the: from > uri="properties:{{queue.efilebatch.request.submitted}}" -->* >             >             >             uri="properties:{{ftp.efilebatch.request.submitted}}?fileName=${header.JMSCorrelationID}.xml" > /> >

Re: FTP producer and exception or transaction

-- View this message in context: http://camel.465427.n5.nabble.com/FTP-producer-and-exception-or-transaction-tp4902912p4926428.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: FTP producer and exception or transaction

Any caveats with upgrading this way? >> > >> >> Are you using transacted JMS ? >> >> If not then the message is pulled off the queue immediately when Camel >> receives the message. >> You can use transacted JMS to have the message support rollback / commit. >> >>

Re: FTP producer and exception or transaction

MQ's lib? Any caveats with upgrading this way? > > > > Are you using transacted JMS ? > > If not then the message is pulled off the queue immediately when Camel > receives the message. > You can use transacted JMS to have the message support rollback / commit. > > > &

Re: FTP producer and exception or transaction

ing this way? > Are you using transacted JMS ? If not then the message is pulled off the queue immediately when Camel receives the message. You can use transacted JMS to have the message support rollback / commit. > Thanks > > -- > View this message in context: &g

FTP producer and exception or transaction

e queue if FTP is unavailable? If not can I use a transaction tag? 3. Is upgrading to Camel 2.5 as easy as replacing the Camel jars in ActiveMQ's lib? Any caveats with upgrading this way? Thanks -- View this message in context: http://camel.465427.n5.nabble.com/FTP-producer-and-exception