Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.Ce contenu n'est pas disponible dans la langue sélectionnée.
7.2. Event Message
Event Message
Copier lienLien copié sur presse-papiers!
					Camel supports the Event Message from the Introducing Enterprise Integration Patterns by supporting the Message 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.
				
Explicitly specifying InOnly
Copier lienLien copié sur presse-papiers!
					If you are using a component which defaults to InOut you can override the Message Exchange Pattern for an endpoint using the pattern property.
				
foo:bar?exchangePattern=InOnly
foo:bar?exchangePattern=InOnly
					From 2.0 onwards on Camel you can specify the Message Exchange Pattern using the dsl.
				
					Using the Fluent Builders
				
from("mq:someQueue").
  inOnly().
  bean(Foo.class);
from("mq:someQueue").
  inOnly().
  bean(Foo.class);
					or you can invoke an endpoint with an explicit pattern
				
from("mq:someQueue").
  inOnly("mq:anotherQueue");
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="bean:foo"/>
</route><route>
    <from uri="mq:someQueue"/>
    <inOnly uri="mq:anotherQueue"/>
</route>
<route>
    <from uri="mq:someQueue"/>
    <inOnly uri="mq:anotherQueue"/>
</route>