This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Versions Compared

Key

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

Message Bus

Camel supports the Message Bus from the EIP patterns. You could view Camel as a Message Bus itself as it allows producers and consumers to be decoupled.

Folks often assume that a Message Bus is a JMS though so you may wish to refer to the JMS component for traditional MOM support.
Also worthy of note is the XMPP component for supporting messaging over XMPP (Jabber)

Of course there are also ESB products such as Apache ServiceMix which serve as full fledged message busses.
You can interact with Apache ServiceMix from Camel in many ways, but in particular you can use the NMR or JBI component to access the ServiceMix message bus directly.

 

Example

The following demonstrates how the Camel message bus can be used to communicate with consumers and producers


Using the Fluent Builders

Code Block
languagejava
from("direct:start")
	.pollEnrich("file:inbox?fileName=data.txt")
	.to("jms:queue:foo");

 

Using the Spring XML Extensions

Code Block
languagexml
<route>
	<from uri="direct:start"/>
	<pollEnrich uri="file:inbox?fileName=data.txt"/>
	<to uri="jms:queue:foo"/>
</route>

Include Page
Using This Pattern
Using This Pattern