Red Hat Training

A Red Hat training course is available for Red Hat Fuse

Chapter 20. Introduction to the Apache CXF Binding Component

Abstract

The Apache CXF binding component allows you to create SOAP/HTTP and SOAP/JMS endpoints.
Important
The Java Business Integration components of Red Hat JBoss Fuse are considered deprecated. You should consider migrating any JBI applications to OSGi.

Overview

The Apache CXF binding component provides connectivity to external endpoints using either SOAP/HTTP or SOAP/JMS. The endpoints are defined using WSDl files that contain Apache CXF specific extensions for defining the transport. In addition, you can add Apache CXF-based Spring configuration to use the advanced features.
It allows for the creation of two types of endpoint:
consumer endpoint
A consumer endpoint listens for messages on a specified address. When it receives a message it sends it to the NMR for delivery to the appropriate endpoint. If the message is part of a two-way exchange, then the consumer endpoint is also responsible for returning the response to the external endpoint.
For information about configuring consumer endpoints see Chapter 28, Consumer Endpoints.
provider endpoint
A provider endpoint receives messages from the NMR. It then packages the message as a SOAP message and sends it to the specified external address. If the message is part of a two-way message exchange, the provider endpoint waits for the response from the external endpoint. The provider endpoint will then direct the response back to the NMR.
For information about configuring provider endpoints see Chapter 29, Provider Endpoints.

Key features

The Apache CXF binding component has the following features:
  • HTTP support
  • JMS 1.1 support
  • SOAP 1.1 support
  • SOAP 1.2 support
  • MTOM support
  • Support for all MEPs as consumers or providers
  • SSL support
  • WS-Security support
  • WS-Policy support
  • WS-RM support
  • WS-Addressing support

Steps for working with the Apache CXF binding component

Using the Apache CXF binding component to expose SOAP endpoints usually involves the following steps:
  1. Defining the contract for your endpoint in WSDL.
    See ???.
  2. Configuring the endpoint and packaging it into a service unit.
    See ???.
  3. Bundling the service unit into a service assembly for deployment into the Red Hat JBoss Fuse container.

More information

For more information about using Apache CXF to create SOAP endpoints see the Apache CXF documentation.