Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 259. 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.

259.1. Dependencies
Copiar enlace

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).

259.2. URI format
Copiar enlace

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.

259.3. URI options
Copiar enlace

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:

259.3.1. Path Parameters (1 parameters):
Copiar enlace

Expand
NameDescriptionDefaultType

appender

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

 

String

259.3.2. Query Parameters (4 parameters):
Copiar enlace

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

259.4. Message body
Copiar enlace

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

259.5. Example usage
Copiar enlace

<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
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat