On Mon, Jun 18, 2012 at 9:36 PM, vishal1981 <vishal.changr...@ericsson.com> wrote: > Hi, > I want to setup Camel as part on of my application being deployed to JBoss > 5.1. My application nests in a bigger ear (which is a company wide umbrella > application) and it contains several modules including 3 of mine - ejb jar, > servlets war and REST API war. There is also an interface jar in the lib > folder of the ear. We are not using Spring but EJB (hibernate and JPA). > This is my first time with Camel and wanted to make sure I got the > deployment right. I intend to use Camel to start and stop several routes > during runtime based on some user selections. > What is the recommended way of deploying Camel in this scenario? Should it > be part of the war or ejb jar? > I am using Camel 2.9.2 ..do I still need the special JBoss Camel component? > Thanks > V >
There is no shoe that fits all. Camel is very flexible, so you can deploy it as you want. In a WAR or as part of EAR. > -- > View this message in context: > http://camel.465427.n5.nabble.com/Pointers-on-setting-up-Camel-on-JBoss-5-1-using-EJBs-Hibernate-tp5714636.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
