The Apache CXF JCA Connector's inbound support makes use of the JCA 1.5 specification's message inflow contract and EJB 2.1 or higher message-driven beans (MDBs). The JCA 1.5 specification defines a framework that allows the Apache CXF JCA Connector to be notified when a MDB starts. The Apache CXF JCA Connector then activates the Fuse Services Framework service endpoint facade, which receives client requests and invokes on the MDB's listener interface.
The instructions in this chapter assume that you are familiar with writing EJBs, including Message Driven Beans and Stateless Session Beans.
![[Note]](imagesdb/note.gif) | Note |
|---|---|
To use the Apache CXF JCA Connector your application server must support JCA 1.5 and EJB 2.1 or higher; for example, WebSphere 6.1. |
For more information about the JCA 1.5 message inflow contract, see Chapter 12, Message Inflow of the JCA 1.5 Specification.
In addition, if you are interested in knowing more about what goes on behind the scenes when a resource adapter, such as the Apache CXF JCA Connector, invokes an application asynchronously through a MDB, see JCA 1.5, Part 3:Message Inflow.
You can use the Apache CXF JCA Connector to expose your J2EE application as a Web service using any of the following scenarios:
Java first, where you implement your service as one of the following:
Message Driven Bean (MDB). In this case, incoming requests do not need to be dispatched to another EJB; the MDB includes the service implementation.
See Service Implemented as a Message Driven Bean for more details.
Stateless Session Bean (SLSB). In this case, you use an Fuse Services Framework-provided generic MDB to dispatch incoming requests to your SLSB.
See Service Implemented as a Stateless Session Bean for more details.
WSDL first, where your starting point is the service WSDL file. You use Fuse Services Framework to generate JAX-WS compliant Java code from the WSDL file and implement your service as a SLSB. Here, again, you use the Fuse Services Framework-provided generic MDB to dispatch incoming requests to your SLSB.
See WSDL First—Service Implemented as a SLSB for more details.
The rest of this chapter describes these scenarios in more detail.
 |  |  |
 |
