Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
camel-jbossAvailable as of Camel 2.1 The camel-jboss is a component which allows you to run Camel inside JBoss Application Server. This component is needed due JBoss classloading challenges. JBoss version If you are using JBoss 4.x/5.x then you need to use The resolver is provided in the class Camel 2.8 onwards From Camel 2.8 onwards there is no longer the need for using this camel-jboss component as Camel is now capable of loading type converters without package scanning. This requires though that all 3rd party components with type converter must define the name of the converter classes as FQN in the Using with Java DSLYou need to configure the resolver on the CamelContext which is done like this: PackageScanClassResolver jbossResolver = new JBossPackageScanClassResolver(); CamelContext context = new DefaultCamelContext(); context.setPackageScanClassResolver(jbossResolver); Using with Spring XMLWhen using Spring XML its just a matter of defining a spring bean with the JBoss class resolver as shown: <bean id="jbossResolver" class="org.apacheextras.camel.jboss.JBossPackageScanClassResolver"/> <camelContext id="camel" xmlns="http://camel.apache.org/schema/spring"> <route> <from uri="seda:start"/> <to uri="mock:result"/> </route> </camelContext> The Camel Extra project was moved to an official associated Apache site and as part of the migration the package names in the source code must not use <bean id="jbossResolver" class="org.apache.camel.jboss.JBossPackageScanClassResolver"/> DependenciesYou need to get the component from the Camel Extra project as JBoss uses LPGL license which cannot be hosted at Apache. |