[[EventMessage-EventMessage]]
== Event Message

Camel supports the
http://www.enterpriseintegrationpatterns.com/EventMessage.html[Event
Message] from the link:enterprise-integration-patterns.html[EIP
patterns] by supporting the link:exchange-pattern.html[Exchange Pattern]
on a link:message.html[Message] which can be set to *InOnly* to indicate
a oneway event message. Camel link:components.html[Components] then
implement this pattern using the underlying transport or protocols.

image:http://www.enterpriseintegrationpatterns.com/img/EventMessageSolution.gif[image]

The default behaviour of many link:components.html[Components] is InOnly
such as for <<jms-component,JMS>>, <<jms-component,File>> or
<<seda-component,SEDA>>

TIP: See the related link:request-reply.html[Request Reply] message.

[[EventMessage-ExplicitlyspecifyingInOnly]]
=== Explicitly specifying InOnly

If you are using a component which defaults to InOut you can override
the link:exchange-pattern.html[Exchange Pattern] for an endpoint using
the pattern property.

[source]
----
foo:bar?exchangePattern=InOnly
----


=== Samples

From 2.0 onwards on Camel you can specify the
link:exchange-pattern.html[Exchange Pattern] using the DSL.

[source,java]
----
from("mq:someQueue").
  setExchangePattern(ExchangePattern.InOnly).
  bean(Foo.class);
----

or you can invoke an endpoint with an explicit pattern

[source,java]
----
from("mq:someQueue").
  inOnly("mq:anotherQueue");
----

And with XML:

[source,xml]
----
<route>
    <from uri="mq:someQueue"/>
    <inOnly uri="bean:foo"/>
</route>
----

[source,xml]
----
<route>
    <from uri="mq:someQueue"/>
    <inOnly uri="mq:anotherQueue"/>
</route>
----

