Versions Compared

Old Version 2

changes.mady.by.user James Strachan

Saved on

compared with

New Version Current

changes.mady.by.user Paul Gale

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

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

...

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

...

with contents

...

...

(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 The FooComponent can then be auto-injected with resources using the Injector, such as to support Spring based auto-wiring, or to support support @Resource (EJB3 style) injection or Guice style style @Inject injection.

Working with Spring XML

You can configure a component via Spring using the following mechanism...{snippet:id=example|lang=xml|url=camel/trunk/components/camel-jms/src/test/resources/org/apache/camel/component/jms/jmsRouteUsingSpring.xml}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 Due to the auto-discover and injection of components based on their initial use via an endpoint URI you don't have to explicitly add a <fooComponent> element to your Spring XML if you don't want to. However if you do want to then you could use xbean-spring which tries to automate most of this the XML binding work for you.If ; or you could look in camel-spring at at CamelNamespaceHandler you'll see how we handle the Spring XML stuff (warning its kinda hairy code to look at (smile). If you wanted 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