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.
![](http://www.enterpriseintegrationpatterns.com/img/EventMessageSolution.gif)
The default behaviour of many Components is InOnly such as for JMS in EIP Component Reference, File or SEDA in EIP Component Reference
![]() | Related |
---|---|
See the related Request Reply message. |
If you are using a component which defaults to InOut you can override the Exchange Pattern for an endpoint using the pattern property.
foo:bar?exchangePattern=InOnly
From 2.0 onwards on Camel you can specify the Exchange Pattern using the dsl.
Using the Fluent Builders
from("mq:someQueue"). inOnly(). bean(Foo.class);
or you can invoke an endpoint with an explicit pattern
from("mq:someQueue"). inOnly("mq:anotherQueue");
Using the Spring XML Extensions
<route> <from uri="mq:someQueue"/> <inOnly uri="bean:foo"/> </route>
<route> <from uri="mq:someQueue"/> <inOnly uri="mq:anotherQueue"/> </route>