There is one limitation until now when you need to work with Camel Transactional Routes as Camel uses TransactionErrorHandler ( http://camel.apache.org/transactionerrorhandler.html). This TxErrorHandler uses behind the scene Spring to handle the Transactions and need to be changed in the future to become pluggable and able to run with Spring, Blueprint, CDI.
On Tue, Jun 4, 2013 at 8:04 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > Camel and CXF support Blueprint which can do the same thing as Spring > does. Did you have a chance to try it? > > 发自我的 iPhone > > 在 2013-6-3，下午6:59，Jose <jagavi...@gmail.com> 写道： > > > Hi, I am trying to use Camel without Spring and I am wondering if there > are > > some limitations. I guess the configuration would be more complicated > but I > > wonder if I will loose some features. > > > > In particular, I am planning to use Camel with CXF. All the examples > that I > > have seen use Camel with Spring. > > > > Thanks a lot. > > > > Jose > > > > > > > > > > -- > > View this message in context: > http://camel.465427.n5.nabble.com/Camel-without-Spring-Limitations-tp5733686.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
