Camel With EJB


If you have installed a Fuse service works installation of EJB and chose not to use the switchyard integration platform but use the camel that comes bundled with it for your integration application, this blog will guide you through the set up process.


Jboss FSW installation, Jboss developer studio or eclipse

Bootstrapping the camel context

There are many ways of doing something on startup when it comes to a EE application. The easiest way (atleast to me) is the singleton startup stateless session bean. Slap on a couple of annotations to your class and you are on your merry way. The application if using cxf will however will not deploy as the installation has some missing jar files. The deployment will flame out complaining about header filter


Fixing the deployment

Since we are using the cxf component, the deployment will complain about not being able to find the class The exception you will see is below

Caused by: java.lang.ClassNotFoundException: org.apache.camel.component.cxf.common.header.CxfHeaderFilterStrategy from [Module "org.apache.camel.cxf:main" from local module loader @2f41b041 (finder: local module finder @19a93a4 (roots: /Users/venu/jboss-eap-6.1/modules,/Users/venu/jboss-eap-6.1/modules/system/layers/soa,/Users/venu/jboss-eap-6.1/modules/system/layers/sramp,/Users/venu/jboss-eap-6.1/modules/system/layers/base))]
	at org.jboss.modules.ModuleClassLoader.findClass( [jboss-modules.jar:1.2.2.Final-redhat-1]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked( [jboss-modules.jar:1.2.2.Final-redhat-1]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked( [jboss-modules.jar:1.2.2.Final-redhat-1]
	at org.jboss.modules.ConcurrentClassLoader.performLoadClass( [jboss-modules.jar:1.2.2.Final-redhat-1]

If we learnt the hard way that reading the exceptions is a helpful excercise, we need to add the following jar file camel-cxf-transport-2.16.1 to the org.apache.camel.cxf module and update the module.xml file with the following

. You can download the the file from Maven-repo

After this, it will start whining about modules not being available as dependencies. You would need to add the following entries in the module.xml file to get it to resolve all of its class path dependencies

 <module name=""/>

 <module name="javax.jws.api"/>

 <module name="javax.wsdl4j.api"/>

This should resolve all the class path issues.

Written on January 1, 2016