Re: Non-Spring Transaction Manager

2009-03-24 Thread James Strachan
2009/3/24 James Strachan : > I think the issue is that you configure the configuration of the JMS > component with the transaction manager after you've created the JMS > endpoint. Try moving the configuration of the JMS component to the > setup method; before you create any endpoints? Just for som

Re: Non-Spring Transaction Manager

2009-03-24 Thread James Strachan
I think the issue is that you configure the configuration of the JMS component with the transaction manager after you've created the JMS endpoint. Try moving the configuration of the JMS component to the setup method; before you create any endpoints? 2009/3/24 Colin Ruthven : > Thought you'd ask.

Re: Non-Spring Transaction Manager

2009-03-24 Thread Colin Ruthven
Thought you'd ask. :) It reflects some exploration of a couple of Camel API's, rather than being stripped to a minimum. Thanks again for helping. Colin public class DataCamelTest extends TestCase{ CamelContext context; ProducerTemplate prod; Endpoint end; public DataCamelTest(S

Re: Non-Spring Transaction Manager

2009-03-24 Thread James Strachan
Whats the code using the producer look like? 2009/3/24 Colin Ruthven : > Thanks. That got me further. > > Assuming I use JOTM and use it for transaction control within Java, I > attempted the following applicationContext.xml : > >   >   >   > >   class="org.springframework.transaction.jta.JotmFact

Re: Non-Spring Transaction Manager

2009-03-24 Thread Colin Ruthven
Thanks. That got me further. Assuming I use JOTM and use it for transaction control within Java, I attempted the following applicationContext.xml : class="org.springframework.transaction.jta.JotmFactoryBean"/> class="org.springframework.transaction.jta.JtaTransactionManager">

Re: Non-Spring Transaction Manager

2009-03-24 Thread James Strachan
2009/3/23 Colin Ruthven : > I don't specifically have one in mind. > > In exploring Camel I found that one can perform the basic messaging > functions in Java using Camel API's only but got messy with transactions. > > My preference would be for Camel to expose a JTA. If that transparently > invoke

Re: Non-Spring Transaction Manager

2009-03-23 Thread Colin Ruthven
I don't specifically have one in mind. In exploring Camel I found that one can perform the basic messaging functions in Java using Camel API's only but got messy with transactions. My preference would be for Camel to expose a JTA. If that transparently invoked Spring TX that would be fine - a

Re: Non-Spring Transaction Manager

2009-03-23 Thread Claus Ibsen
On Mon, Mar 23, 2009 at 5:06 PM, Colin Ruthven wrote: > Is it possible to use transactions in Camel messaging (eg JMS) without > Spring intruding? Camel may use Spring underneath the covers but I don't > want to use it inside my application. > > Or at least only use Camel API's to do this or be ab

Non-Spring Transaction Manager

2009-03-23 Thread Colin Ruthven
Is it possible to use transactions in Camel messaging (eg JMS) without Spring intruding? Camel may use Spring underneath the covers but I don't want to use it inside my application. Or at least only use Camel API's to do this or be able to plug other solutions in. The documentation seems to