Versions Compared

Key

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

JBI components are slightly heavyweight objects; there's a bit of plumbing required for the component developer to write. To make things easier for the developer, we support POJOs. In addition we provide a PojoSupport and ComponentSupport classes making it easy to write new POJOs or components with very little code.

MessageExchangeListener interface

To be able to receive new message exchanges easily, rather than writing a new thread, just implement this interface. Its analagous to the JMS MessageListener interface. The ServiceMix container will detect the use of this interface and be able to perform immediate dispatch (rather than the default JBI asynchronous dispatch model where a thread is used per JBI component).

...

Lazily creates a default MessageExchangeFactory. Create your own factory instances for specific services / endpoints.

getBody() and setBody()

These methods allow you to get and set the message body as a POJO using whatever marshaling mechanism is being used. e.g. if a JavaSource is used for the body or some XML marshaling tool like XStream or JAXB is used then these helper methods provide access to the underlying POJO.

service and endpoint properties

...