On Wed, Feb 27, 2013 at 10:20 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> On Thu, Feb 28, 2013 at 1:22 AM, Chris Geer <ch...@cxtsoftware.com> wrote: > > On Wed, Feb 27, 2013 at 5:16 PM, Guillaume Nodet <gno...@gmail.com> > wrote: > > > >> Getting rid of spring transaction support and implementing our own > layer in > >> camel would be a big win, as it's really a big missing feature in > >> blueprint. > >> I'm willing to pay a beer to anyone tackling that in 2.12 ... > >> > >> Btw, what's your need for getting rid of spring transaction ? Is that > also > >> to remove the dependency on spring ? Because that one already supports > >> plain JTA. > >> > > > > My big driver right now is that I can use JTA transactions for everything > > except Camel JMS/ActiveMQ. I'm curious about your statement about it > > already supporting JTA. Looking at the JmsComponent, it takes a > > PlatformTransactionManager (i.e. Spring) not a TransactionManager (JTA). > > > > If I could use a standard transaction manager right now I'd be ok for > now. > > Eventually I'd like to be able to run without spring at all though. > > > > You should use camel-sjms instead, its the JMS component without > spring dependencies. > You can use JTA transactions with that. > Claus, For the moment we are still on Camel 2.10.x so SJMS isn't quite an option. We are also making use of XA transactions (we use the activemq components which extends from JMS component) at the moment so it doesn't look like SJMS is going to fit. I'll keep it in mind as we progress into Camel 2.11+. The ActiveMQ component with the Spring PlatformTransactionManager is working right now so we don't have to switch today. Thanks, Chris > > > >> > >> > >> On Wed, Feb 27, 2013 at 9:50 PM, Chris Geer <ch...@cxtsoftware.com> > wrote: > >> > >> > On Wednesday, February 27, 2013, Henryk Konsek wrote: > >> > > >> > > Hi Chris, > >> > > > >> > > > 1) Refactor the JMS Component to use JTA transactions instead of > >> Spring > >> > > > Transactions. > >> > > > >> > > I'm not really sure if we need to include such kind of changes in > >> > > Camel 3 roadmap. The idea is good, but can't we just raise Jira > issue > >> > > for it? And implement, even in Camel 2? :) > >> > > >> > > >> > Sure, it could be done in 2.x but 3.0 makes more sense to me because > it > >> > would be a breaking change. An alternative would be to support both > JTA > >> > transactions and spring transactions and deprecate spring eventually > but > >> > that could be a pain. Either way I can create the JIRA. > >> > > >> > > > >> > > Best regards. > >> > > > >> > > -- > >> > > Henryk Konsek > >> > > http://henryk-konsek.blogspot.com > >> > > > >> > > >> > >> > >> > >> -- > >> ------------------------ > >> Guillaume Nodet > >> ------------------------ > >> Red Hat, Open Source Integration > >> > >> Email: gno...@redhat.com > >> Web: http://fusesource.com > >> Blog: http://gnodet.blogspot.com/ > >> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen >
