Versions Compared

Old Version 5

changes.mady.by.user Claus Ibsen

Saved on

compared with

New Version Current

changes.mady.by.user Carsten Ringe

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Info
titleJBoss version

If you are using JBoss 4.x/5.x then you need to use camel-jboss JAR. If you are using JBoss 6.x then you need to use camel-jboss6 JAR.

The resolver is provided in the class org.apacheapacheextras.camel.jboss.JBossPackageScanClassResolver in the camel-jboss jar file.

Info
titleCamel 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 META-INF/org/apache/camel/TypeConverter file. See more details at Type Converter.
One exception is if you are using Bindy component as it still needs this JBoss resolver.

Using with Java DSL

You need to configure the resolver on the CamelContext which is done like this:

...

Code Block
xml
xml
   <bean id="jbossResolver" class="org.apachextraapacheextras.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 org.apache so we renamed the packages as shown above. But if you are using the older versions of the JAR files then you need to use as shown below:

...