Versions Compared

Key

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

Pojo Component

The pojo: component binds PojoExchanges to method invocations on Java Objects.

URI format

Code Block

pojo:someName

Where someName can be any string to uniquely identify the endpoint

Using

Object instance that can receive invocations, must be explicitly registered with the PojoComponent.

Wiki Markup
{snippet:id=register|lang=java|url=activemq/camel/trunk/camel-core/src/test/java/org/apache/camel/component/pojo/PojoRouteTest.java}

Once an endpoint has been registered, you can build Camel routes that use it to process exchanges.

Wiki Markup
{snippet:id=route|lang=java|url=activemq/camel/trunk/camel-core/src/test/java/org/apache/camel/component/pojo/PojoRouteTest.java}

A pojo: endpoint cannot be defined as the input to the route. Consider using a direct: or queue: endpoint as the input for a PojoExchange. You can use the createProxy() methods on PojoComponent to create a proxy that will generate PojoExchanges and send them to any endpoint:

...

is now just an alias for the Bean component.

Has been removed in Camel 2.0.

Include Page
Endpoint See Also
Endpoint See Also

...