This allows you to use a plugable Marshaler to map your POJOs to JAXP Sources.

Sending Messages
This example uses a specific service to make an invocation call:

Map properties = new HashMap();
properties.put("name", "James");
// lets use a specific service to route to
QName service = new QName("http://servicemix.org/cheese/", "receiver");
EndpointResolver resolver = client.createResolverForService(service);
client.send(resolver, null, properties, "<hello>world</hello>");

In the next example, we assume that the JBI container will have set up a default routing connection for our client, so there is no requirement to specify the endpoint.

Map properties = new HashMap();
properties.put("name", "James");
client.send(null, null, properties, "<hello>world</hello>");

Invoking Services with InOut

// optional endpoint resolution
EndpointResolver resolver = client.createResolverForService(service);
Map properties = new HashMap();
properties.put("name", "James");

Object response = client.request(resolver, null, properties,
"<hello>world</hello>");

Example Using JMS and XSLT
Here's a quick example to show you some of the Service-Mix integration capabilities in action. We consume messages using JCA, then transform them with XSLT and send them to a new destination using JMS.

Let's set up a JBI component to consume from JCA using JMS:

<component id="myJmsReceiver" service="foo:myJmsReceiver"
class="org.servicemix.components.jms.JmsInUsingJCABinding"
destinationService="foo:transformer">

<property name="jcaContainer" ref="activeJcaContainer"/>

<property name="activationSpec">
  <bean class="org.activemq.ra.ActiveMQActivationSpec">
<property name="destination" value="test.org.servicemix.example.jca/>
  <property name="destinationType" value ="javax.jms.Topic"/>
  </bean>
  </property>
</component>

Let's transform the message

<component id="transformer" service="foo:trans
former" class="org.servicemix.components.xslt.XsltComponent"
destinationService="foo:transformedSender">
<property name="xsltResource" value="classpath:org/servicemix/
components/xslt/transform.xsl"/>
</component>

Now let's send the message using the Spring JmsTemplate

<component id="myJmsSender" service="foo:myJmsSender" class="org.
servicemix.components.jms.JmsSenderComponent">
<property name="template">
<bean class="org.springframework.jms.core.JmsTemplate">
<property name="connectionFactory">
<ref local="jmsFactory"/>
</property>
<property name="defaultDestinationName" value="test.org.
servicemix.components.xslt.source"/>
<property name="pubSubDomain" value="true"/>
</bean>
</property>
</component>

Scripting Support
ServiceMix also supports scripting languages through JSR 223 - Scripting for Java. Here are some examples using Groovy:

Before we go into detail of how you can work with JBI and Groovy in ServiceMix, lets show a simple hello world kinda example.

<component id="myServiceUsingXMLText" service="foo:myServiceUsingXMLText"
endpoint="myServiceUsingXMLText"
class="org.servicemix.components.groovy.GroovyComponent">
  <property name="scriptText">
   <value>
    <![CDATA[

// lets output some message properties
outMessage.properties = [foo:"hello", someList:[1, 2, 3]]

// lets output some non-xml body
outMessage.bodyText = """
<hello>
  <world person="$inMessage.properties.name" location="London"/>
</hello>
"""
     ]]>
    </value>
   </property>
  </component>

As you can see the component is configured with a piece of Groovy to execute when the service is invoked.

Now we'll go through the various options which are available when working with JBI and Groovy in ServiceMix.

Maintaining State Across Requests
It's often handy to keep track of state across requests. There is a variable called 'bindings' which you can use to maintain state; here's the groovy...

if (bindings.counter == null) {
  bindings.counter = 1
}
else {
  ++bindings.counter
}

def date = new Date()

outMessage.bodyText = "<response counter='$bindings.counter'
date='$date'></response>"