Child pages
  • Processor
Skip to end of metadata
Go to start of metadata


The Processor interface is used to implement consumers of message exchanges or to implement a Message Translator

Using a processor in a route

Once you have written a class which implements processor like this...

You can then easily use this inside a route by declaring the bean in Spring, say via the XML (or registering it in JNDI if that is your Registry)

Then in Camel you can do

Using the process DSL

In your route you can also use the process DSL syntax for invoking a processor.

If you need to lookup the processor in the Registry then you should use the processRef DSL:

Why use process when you can use to instead?

The process can be used in routes as an anonymous inner class such:

This is usable for quickly whirling up some code. If the code in the inner class gets a bit more complicated it is of course advised to refactor it into a separate class.

Turning your processor into a full Component

There is a base class called ProcessorEndpoint which supports the full Endpoint semantics given a Processor instance.

So you just need to create a Component class by deriving from DefaultComponent which returns instances of ProcessorEndpoint. For more details see Writing Components

See Also

  • No labels