This chapter provides the necessary information about the Camel Subsystem and Deployment Configuration.

Camel Subsystem Configuration

The Camel Subsystem Configuration may contain static system routes. However, the system starts the route automatically.

<subsystem xmlns="urn:jboss:domain:camel:1.0">
   <camelContext id="system-context-1">
     <![CDATA[
     <route>
       <from uri="direct:start"/>
       <transform>
         <simple>Hello #{body}</simple>
       </transform>
     </route>
     ]]>
   </camelContext>
</subsystem>

Camel Deployment Configuration

If you want to modify the default configuration of your Camel deployment, you can edit either the WEB-INF/jboss-all.xml or META-INF/jboss-all.xml configuration file in your deployment.

Use a <jboss-camel> XML element within the jboss-all.xml file to control the camel configuration.

Disabling the Camel Subsystem

If you do not want to add the camel subsystem into your deployment, set the enabled="false" attribute on the jboss-camel XML element.

Example jboss-all.xml file:

<jboss umlns="urn:jboss:1.0">
  <jboss-camel xmlns="urn:jboss:jboss-camel:1.0" enabled="false"/>
</jboss>

Selecting Components

If you add nested <component> or <component-module> XML elements, then instead of adding the default list of Camel components to your deployment, only the specified components will be added to your deployment.

Example jboss-all.xml file:

<jboss umlns="urn:jboss:1.0">
  <jboss-camel xmlns="urn:jboss:jboss-camel:1.0">
    <component name="camel-ftp"/>
    <component-module name="org.apache.camel.component.rss"/>
  </jboss-camel>
</jboss>