このコンテンツは選択した言語では利用できません。

Chapter 301. Stomp Component


Available as of Camel version 2.12

The stomp: component is used for communicating with Stomp compliant message brokers, like Apache ActiveMQ or ActiveMQ Apollo

Maven users will need to add the following dependency to their pom.xml for this component:

<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-stomp</artifactId>
    <version>x.x.x</version>
    <!-- use the same version as your Camel core version -->
</dependency>
Copy to Clipboard Toggle word wrap

301.1. URI format

stomp:queue:destination[?options]
Copy to Clipboard Toggle word wrap

Where destination is the name of the queue.

301.2. Options

The Stomp component supports 8 options which are listed below.

Expand
NameDescriptionDefaultType

configuration (advanced)

To use the shared stomp configuration

 

StompConfiguration

brokerURL (common)

The URI of the Stomp broker to connect to

 

String

login (security)

The username

 

String

passcode (security)

The password

 

String

host (common)

The virtual host

 

String

useGlobalSslContext Parameters (security)

Enable usage of global SSL context parameters.

false

boolean

headerFilterStrategy (filter)

To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.

 

HeaderFilterStrategy

resolveProperty Placeholders (advanced)

Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.

true

boolean

The Stomp endpoint is configured using URI syntax:

stomp:destination
Copy to Clipboard Toggle word wrap

with the following path and query parameters:

301.2.1. Path Parameters (1 parameters):

Expand
NameDescriptionDefaultType

destination

Required Name of the queue

 

String

301.2.2. Query Parameters (10 parameters):

Expand
NameDescriptionDefaultType

brokerURL (common)

Required The URI of the Stomp broker to connect to

tcp://localhost:61613

String

host (common)

The virtual host name

 

String

bridgeErrorHandler (consumer)

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

false

boolean

exceptionHandler (consumer)

To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.

 

ExceptionHandler

exchangePattern (consumer)

Sets the exchange pattern when the consumer creates an exchange.

 

ExchangePattern

headerFilterStrategy (advanced)

To use a custom HeaderFilterStrategy to filter header to and from Camel message.

 

HeaderFilterStrategy

synchronous (advanced)

Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).

false

boolean

login (security)

The username

 

String

passcode (security)

The password

 

String

sslContextParameters (security)

To configure security using SSLContextParameters

 

SSLContextParameters

You can append query options to the URI in the following format, ?option=value&option=value&…​

301.3. Samples

Sending messages:

from("direct:foo").to("stomp:queue:test");
Copy to Clipboard Toggle word wrap

Consuming messages:

from("stomp:queue:test").transform(body().convertToString()).to("mock:result")
Copy to Clipboard Toggle word wrap

301.4. Endpoints

Camel supports the Message Endpoint pattern using the Endpoint interface. Endpoints are usually created by a Component and Endpoints are usually referred to in the DSL via their URIs.

From an Endpoint you can use the following methods

* createProducer() will create a Producer for sending message exchanges to the endpoint * createConsumer() implements the Event Driven Consumer pattern for consuming message exchanges from the endpoint via a Processor when creating a Consumer * createPollingConsumer() implements the Polling Consumer pattern for consuming message exchanges from the endpoint via a PollingConsumer

301.5. See Also

  • Configuring Camel
  • Message Endpoint pattern
  • URIs
  • Writing Components
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat