[CONF] Apache Camel > Configuring Camel

[confluence]

Configuring Camel Page edited by Claus Ibsen Changes (1) {include:How do I configure endpoints} {include:How do I import routes from other XML files} {include:How do I add a component} Full Content How do I configure endpoints? There are a few different approaches to configuring components and endpoints. Using Java Code You can explicitly configure a Component using Java code as shown in this example Or you can explicitly get hold of an Endpoint and configure it using Java code as shown in the Mock endpoint examples. SomeEndpoint endpoint = (SomeEndpoint) camelContext.getEndpoint("someURI"); endpoint.setSomething("aValue"); Using Guice You can also use Guice as the dependency injection framework. For example see the Guice JMS Example Using Spring XML You can configure your Component or Endpoint instances in your Spring XML as follows. <camelContext id="camel" xmlns="http://camel.apache.org/schema/spring"> </camelContext> <bean id="activemq" class="org.apache.camel.component.jms.JmsComponent"> <property name="connectionFactory"> <bean class="org.apache.activemq.ActiveMQConnectionFactory"> <property name="brokerURL" value="vm://localhost?broker.persistent=false"/> </bean> </property> </bean> Which allows you to configure a component using some name (activemq in the above example), then you can refer to the component using activemq:[queue:|topic:]destinationName. This works by the SpringCamelContext lazily fetching components from the spring context for the scheme name you use for Endpoint URIs Using Endpoint URIs Another approach is to use the URI syntax. The URI syntax supports the query notation. So for example with the Mail component you can configure the password property via the URI pop3://host:port?password=foo Referring beans from Endpoint URIs Available as of Camel 2.0 When configuring endpoints using URI syntax you can now refer to beans in the Registry using the # notation. If the parameter value starts with a # sign then Camel will lookup in the Registry for a bean of the given type. For instance: file://inbox?sorter=#mySpecialFileSorter Will lookup a bean with the id mySpecialFileSorter in the Registry. See Also How do I add a component Spring URIs How do I import routes from other XML files Available as of Camel 2.3 When defining routes in Camel using Xml Configuration you may want to define some routes in other XML files. For example you may have many routes and it may help to maintain the application if some of the routes are in separate XML files. You may also want to store common and reusable routes in other XML files, which you simple can import when needed. In Camel 2.3 this is now possible to define routes outside <camelContext/> which you do in a new <routeContext/> tag. For example we could have a file named myCoolRoutes.xml which contains a couple of routes as shown: myCoolRoutes.xml <!-- this is an included XML file where we only the the routeContext --> <routeContext id="myCoolRoutes" xmlns="http://camel.apache.org/schema/spring"> <!-- we can have a route --> <route id="cool"> <from uri="direct:start"/> <to uri="mock:result"/> </route> <!-- and another route, you can have as many your like --> <route id="bar"> <from uri="direct:bar"/> <to uri="mock:bar"/> </route> </routeContext> Then in your XML file which contains the CamelContext you can use Spring to import the myCoolRoute.xml file. And then inside <camelContext/> you can refer to the <routeContext/> by its id as shown below: <!-- import the routes from another XML file --> <import resource="myCoolRoutes.xml"/> <camelContext id="myCamel" xmlns="http://camel.apache.org/schema/spring"> <!-- refer to a given route to be used --> <routeContextRef ref="myCoolRoutes"/> <!-- we can of course still use routes inside camelContext --> <route id="inside"> <from uri="direct:inside"/> <to uri="mock:inside"/> </route> </camelContext> Also notice that you can mix and match, having routes inside CamelContext and also externalized in RouteContext. You can have as many <routeContextRef/> as you like. Reusable routes The routes defined in <routeContext/> can be reused by multiple <camelContext/>. Hover its only the definition which is reused. At runtime each CamelContext will creates its own instance of the route based on the definition. How do I add a component You might first want to read Writing Components for a background in how to implement a new component. Typically it means you write an implementation of the Component interface, usually deriving from DefaultComponent. You can then register your component explicitly via CamelContext context = new DefaultCamelContext(); context.addComponent("foo", new FooComponent(context)); However you can use the auto-discovery feature of Camel where by Camel will automatically add a Component when an endpoint URI is used. To do this you would create a file called /META-INF/services/org/apache/camel/component/foo with contents class=org.acme.FooComponent (you can add other property configurations in there too if you like) Then if you refer to an endpoint as foo://somethingOrOther Camel will auto-discover your component and register it. The FooComponent can then be auto-injected with resources using the Injector, such as to support Spring based auto-wiring, or to support @Resource (EJB3 style) injection or Guice style @Inject injection. Working with Spring XML You can configure a component via Spring using the following mechanism... <camelContext id="camel" xmlns="http://camel.apache.org/schema/spring"> </camelContext> <bean id="activemq" class="org.apache.camel.component.jms.JmsComponent"> <property name="connectionFactory"> <bean class="org.apache.activemq.ActiveMQConnectionFactory"> <property name="brokerURL" value="vm://localhost?broker.persistent=false"/> </bean> </property> </bean> Which allows you to configure a component using some name (activemq in the above example), then you can refer to the component using activemq:[queue:|topic:]destinationName. If you want to add explicit Spring 2.x XML objects to your XML then you could use the xbean-spring which tries to automate most of the XML binding work for you; or you could look in camel-spring at CamelNamespaceHandler you'll see how we handle the Spring XML stuff (warning its kinda hairy code to look at . If you wanted <fooComponent> to be a standard part of the core Camel schema then you'd hack that file to add your component & conftribute a patch to the camel XSD. Otherwise you could write your own namespace & schema if you prefer. See Also Writing Components How do I configure endpoints Change Notification Preferences View Online | View Changes | Add Comment