Hi， Camel transaction support is based on Spring transaction framework, even you are tend to use Java DSL. We could let the Spring to load the Camel route which you defined in Java just like this[1]
[1]http://camel.apache.org/spring.html#Spring-UsingJavaCode -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wednesday, November 6, 2013 at 12:56 PM, kraythe . wrote: > Greetings, > > I have a route that needs to call a database, read some records, format > them and put them into ActiveMQ. Naturally the best way to do this would be > to wrap the whole thing in a transacted route. However, I do not want to > use SpringXML as a route builder interface at all. I don't think its as > expressive or flexible as the fluent builders. > > The application will be running in a WAR in JBoss EAP 6.1.1 and using > servletcontextlistener to bootstrap camel. Although I might have to > tolerate some print intrusion I am generally not a fan of IOC spring taking > over whole applications. > > So what would be the best way to accomplish this? > > *Robert Simmons Jr. MSc.* > *Author of: Hardcore Java (2003) and Maintainable Java (2012)* > *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 > <http://www.linkedin.com/pub/robert-simmons/40/852/a39>*
