Event Message

Camel supports the Event Message from the EIP patterns by supporting the Exchange Pattern on a Message which can be set to InOnly to indicate a oneway event message. Camel Components then implement this pattern using the underlying transport or protocols.

The default behaviour of many Components is InOnly such as for JMS, File or SEDA


See the related Request Reply message.

Explicitly specifying InOnly

If you are using a component which defaults to InOut you can override the Exchange Pattern for an endpoint using the pattern property.


From 2.0 onwards on Camel you can specify the Exchange Pattern using the DSL.

Using the Fluent Builders


or you can invoke an endpoint with an explicit pattern


Using the Spring XML Extensions

    <from uri="mq:someQueue"/>
    <inOnly uri="bean:foo"/>
    <from uri="mq:someQueue"/>
    <inOnly uri="mq:anotherQueue"/>

Using This Pattern

If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.

  • No labels