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. 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/
