You can define the aggregator and processor just as you do with spring. As Camel has a set of internal modules, which can be unmarshalled from the xml with JAXB, to implement the EPI. We just need to tell JndiCamelServletContextListener to load these routes xml this time. The route definition is same with the one that we use in Spring.
The only short coming of this approach is you cannot create multiple camel context unless you change the code of JndiCamelServletContextListener. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 8, 2014 at 2:27:16 AM, yogu13 (yogesh....@synechron.com) wrote: > Hi, > > I am checking out on the possibility of using camel without spring... I was > looking at the examples available on this regard and could only find > http://camel.apache.org/servlet-tomcat-no-spring-example.html. The example > shown is quite simple which doesnt involve any processor, aggregrator etc. > > I wanted to know would all the components and features of camel be available > when working without spring or is there any limitation to this? > > Also any pointers if i just want to add a processor to the example in the > link then how would the camel config look like ? > > Thank you! > > Regards, > -Yogesh > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Using-camel-without-spring-tp5760251.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
