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

Chapter 242. OSGi PAX Logging Component


Available as of Camel version 2.6

The paxlogging component can be used in an OSGi environment to receive PaxLogging events and process them.

242.1. Dependencies

Maven users need to add the following dependency to their pom.xml

<dependency>
  <groupId>org.apache.camel</groupId>
  <artifactId>camel-paxlogging</artifactId>
  <version>${camel-version}</version>
</dependency>
Copy to Clipboard Toggle word wrap

where ${camel-version} must be replaced by the actual version of Camel (2.6.0 or higher).

242.2. URI format

paxlogging:appender[?options]
Copy to Clipboard Toggle word wrap

where appender is the name of the pax appender that need to be configured in the PaxLogging service configuration.

242.3. URI options

The OSGi PAX Logging component supports 2 options which are listed below.

Expand
NameDescriptionDefaultType

bundleContext (consumer)

The OSGi BundleContext is automatic injected by Camel

 

BundleContext

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 OSGi PAX Logging endpoint is configured using URI syntax:

paxlogging:appender
Copy to Clipboard Toggle word wrap

with the following path and query parameters:

242.3.1. Path Parameters (1 parameters):

Expand
NameDescriptionDefaultType

appender

Required Appender is the name of the pax appender that need to be configured in the PaxLogging service configuration.

 

String

242.3.2. Query Parameters (4 parameters):

Expand
NameDescriptionDefaultType

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

synchronous (advanced)

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

false

boolean

242.4. Message body

The in message body will be set to the received PaxLoggingEvent.

242.5. Example usage

<route>
    <from uri="paxlogging:camel"/>
    <to uri="stream:out"/>
</route>
Copy to Clipboard Toggle word wrap

Configuration:

log4j.rootLogger=INFO, out, osgi:VmLogAppender, osgi:camel
Copy to Clipboard Toggle word wrap
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

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

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

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

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

会社概要

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

Theme

© 2025 Red Hat