7.2. Event Message

download PDF

Event Message

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.
The default behaviour of many Components is InOnly such as for JMS, File or SEDA

Explicitly specifying InOnly

If you are using a component which defaults to InOut you can override the Message Exchange Pattern for an endpoint using the pattern property.
From 2.0 onwards on Camel you can specify the Message Exchange Pattern using the dsl.
Using the Fluent Builders
or you can invoke an endpoint with an explicit pattern
    <from uri="mq:someQueue"/>
    <inOnly uri="bean:foo"/>
    <from uri="mq:someQueue"/>
    <inOnly uri="mq:anotherQueue"/>
Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.