...

ServiceMix CXF SE

ServiceMix Cxf Se CXF SE component is a JBI Service Engine exposing (annotated) POJO as services on the JBI Bus.

It uses apache cxf Apache CXF internally to perform service invocations and xml marshaling.

Features:

• jsr181 JSR-181 annotations
• jaxb2 binding
• JAXB2/Aegis/XMLBeans databinding
• WSDL auto generation
• Java proxy supportwsdl auto generation
• MTOM / attachments support

Installation

Maven Archetype

You can use Installing the servicemix-cxf-se component can be done in several ways:

• drop the installer zip in an hotdeploy directory monitored by ServiceMix
• using ant tasks

Note that when using ant tasks, the component is not started, you will have to start it manually using ant tasks or a console.

Deployment

You can deploy Service Units containing a file named xbean.xml for activating consumer and provider endpoints.

This xml file should respect the given syntax, though this is a spring based xml configuration file
See a full example here.  Note that you have to define the cxf-se namespace with

...

<beans xmlns:cxfse="http://servicemix.apache.org/cxfse/1.0">
    ...
</beans>

-service-unit archetype to create a CXF SE Service Unit (including a sample POJO):

mvn archetype:create \
  -DarchetypeGroupId=org.apache.servicemix.tooling \
  -DarchetypeArtifactId=servicemix-cxf-se-service-unit \
  -DarchetypeVersion=2010.01 \
  -DgroupId=your.group.id \
  -DartifactId=your.artifact.id \
  -Dversion=your-version

Once you've customized the service unit, simply install the SU:

mvn install

<dependency>
  <groupId>your.group.id</groupId>
  <artifactId>your.artifact.id</artifactId>
  <version>your-version</version>
</dependency>

Endpoint Configuration

The CXF SE endpoint provides a property named pojo. You can expose any POJO which contains the @WebService annotation.

A simple example follows

Any numbers of endpoints can be specified in the xbean.xml file.

As the main purpose is to expose a POJO, you will have to include the needed class files / jars in the service unit and reference them using the following tags in your xbean.xml configuration file:

<classpath>
  <location>.</location>
</classpath>

This will add the content of the location tags (relative to the unzipped service unit) to the classpath. The previous configuration will just add the class files contained in the service unit, as if it is a plain jar.

If you want to embed jars, just use something like

<classpath>
  <location>lib/foo.jar</location>
</classpath>

Endpoint

A few examples:

<cxfse:endpoint>
   <cxfse:pojo>
     <bean class="org.apache.cxf.calculator.CalculatorImpl">
     </bean>
   </cxfse:pojo>
</cxfse:endpoint>

You can use a proxy (see Proxies section of this page):

<cxfse:endpoint>
  <cxfse:pojo>
     <bean class="org.apache.servicemix.cxfse.GreeterImplForClientProxy">
       <property name="calculator">
          <cxfse:proxy service="calculator:CalculatorService" context="#context" type="org.apache.cxf.calculator.CalculatorPortType" />
       </property>
     </bean>
 </cxfse:pojo>
</cxfse:endpoint>

Accessing the JBI bus

The prefered way to access the JBI bus is by retrieving a ComponentContext implementation.
If you want to get ComponentContext implementation injected into your POJO, and send a request to another service from your POJO, you need add the following method on your POJO:

...

You can find a whole context injection test case here

Lightweight mode

The servicemix-cxf-se component can also be configured in a spring/xbean configuration file, for use in an embedded ServiceMix.
Here is an example of such a configuration:

<sm:activationSpec>
  <sm:component>
      <cxfse:component>
      	<cxfse:endpoints>
           <cxfse:endpoint>
              <cxfse:pojo>
                 <bean class="org.apache.cxf.calculator.CalculatorImpl"/>
              </cxfse:pojo>
           </cxfse:endpoint>
      	</cxfse:endpoints>
      </cxfse:component>
  </sm:component>
</sm:activationSpec>

...

...

Proxies

You can create java proxies for JBI endpoints, provided that they expose a WSDL.

...

You can use it from one of you client bean, or from inside another component, and call the JBI endpoint as a plain Java object.

From a CXF SE From a cxfse Service Unit, it could be used as following:

...

You can find a complete proxy test case here

MTOM support

MTOM is a way to handle large amounts of binary data in your services. Unlike attachments, the XML infoset stays the same. MTOM just "optimizes" any base64Binary data you have in your messages. When MTOM is turned on, this base64 data gets sent as a binary attachment saving time and space.

...

MTOM is supported for the following classes:

• DataSource
• DataHandler
• Wiki Markupbyte\[\]

If you have a bean with the following method:

...

provided that the JBI message contains an attachment named "binary".

You can find a complete MTOM test case here

Interceptors Configuration

Since cxfse is using apache cxf Apache CXF internally, so you can configure cxf se endpoint with inteceptors which follow cxf inteceptor api.
example per as below

<cxfse:endpoint>
        <cxfse:pojo>inFaultInterceptors>
          <bean class="org.apache.cxf.calculatorinterceptor.CalculatorImplLoggingInInterceptor"/>
          </bean>

        </cxfse:pojo>inFaultInterceptors>
        <cxfse:inInterceptors>
          <bean class="org.apache.cxf.interceptor.LoggingInInterceptor"/>
        </cxfse:inInterceptors>
        <cxfse:outInterceptors>outFaultInterceptors>
          <bean class="org.apache.cxf.interceptor.LoggingOutInterceptor"/>
        </cxfse:outInterceptors>outFaultInterceptors>
        <cxfse:inFaultInterceptors>outInterceptors>
          <bean class="org.apache.cxf.interceptor.LoggingInInterceptorLoggingOutInterceptor"/>
        </cxfse:inFaultInterceptors>
      outInterceptors>
  <cxfse:outFaultInterceptors>pojo>
          <bean class="org.apache.cxf.interceptorcalculator.LoggingOutInterceptorCalculatorImpl"/>
    </bean>
    </cxfse:outFaultInterceptors>
      pojo>
</cxfse:endpoint>

Can find document for cxf CXF interceptors here