Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Information added on Java-coded configuration of the bus

...

The Bus is the backbone of CXF architecture. It manages extensions and acts as an interceptor provider. The interceptors for the bus will be added to the respective inbound and outbound message and fault interceptor chains for all client and server endpoints created on the bus (in it's its context).
By default, it contributes no interceptors to either of these interceptor chain types. To change this, but they can be added via configuration files or with Java code, as shown below.

Note: For endpoint-specific configuration (as opposed to configuration for all for endpoints created by the CXF bus), look at the Logging Messages section for code samples.

Using a Configuration File

Here, simply define a bus element in your Spring configuration file, and add child elements as required,for example:

...

Name

Value

inInterceptors

The interceptors contributed to inbound message interceptor chains. A list of <bean>s or <ref>s.

inFaultInterceptors

The interceptors contributed to inbound fault interceptor chains. A list of <bean>s or <ref>s.

outInterceptors

The interceptors contributed to outbound message interceptor chains. A list of <bean>s or <ref>s.

outFaultInterceptors

The interceptors contributed to outbound fault interceptor chains. A list of <bean>s or <ref>s.

features

The features applied to the bus. A list of <bean>s or <ref>s. See here for a list of available features.

Programmatic Configuration

Although usually less convenient, interceptors can be added to the bus with Java code. See this code sample for an example.

Extending the Bus

TODO: Explain how to add a custom bus extension (META-INF/cxf/cxf.extension ...).