LibraryLink ToToggle FramesPrintFeedback

Chapter 1. Introduction to the FUSE ESB JMS Binding Component

The FUSE ESB JMS binding component is built using the Spring 2.0 JMS framework. It allows you to create two types of endpoints:

[Note]Note

The JMS binding component also supports non-Spring based endpoints. However, the non-Spring based endpoints are deprecated.

In most instances, you do not need to write any Java code to create endpoints. All of the configuration is done using Spring XML that is placed in an xbean.xml file. There are some instances where you will need to develop your own Java classes to supplement the basic functionality provided by the binding components default implementations. These cases are discussed at the end of this guide.

The FUSE ESB JMS binding component provides a number of enterprise quality features including:

A service unit that configures the JMS binding component will contain two artifacts:

xbean.xml

The xbean.xml file contains the XML configuration for the endpoint defined by the service unit. The contents of this file are the focus of this guide.

[Note]Note

The service unit can define more than one endpoint.

meta-inf/jbi.xml

The jbi.xml file is the JBI descriptor for the service unit. Example 1.1 shows a JBI descriptor for a JMS service unit.

Example 1.1. JBI Descriptor for a JMS Service Unit

<jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0">
  <services binding-component="false" 1
            xmlns:b="http://servicemix.apache.org/samples/bridge"> 2
    <provides service-name="b:jms" 3
              endpoint-name="endpoint"/> 4
    <consumes interface-name="b:MyConsumerInterface"/>  5
  </services>
</jbi>

The elements shown in Example 1.1 do the following:

1

The service element is the root element of all service unit descriptors. The value of the binding-component attribute is always false.

2

The service element contains namespace references for all of the namespaces defined in the xbean.xml file's bean element.

3

The provides element corresponds to a JMS provider endpoint. The service-name attribute derives its value from the service attribute in the JMS provider's configuration.

[Note]Note

This attribute can also appear on a consumes element.

4

The endpoint-name attribute derives its value from the endpoint attribute in the JMS provider's configuration.

[Note]Note

This attribute can also appear on a consumes element.

5

The consumes element corresponds to a JMS consumer endpoint. The interface-name attribute derives its value from the interfaceName attribute in the JMS consumer's configuration.

[Note]Note

This attribute can also appear on a provides element.

The FUSE ESB Maven tooling provides two archetypes for seeding a project whose result is a service unit for the JMS binding component:

The resulting project will contain two generated artifacts:

If you want to add custom marshalers, custom destination choosers, or other custom Java code, you must add a java folder to the generated src folder. You also need to modify the generated pom.xml file to compile the code and package it with the service unit.

To package JMS endpoints as OSGi bundles you need to make two minor changes:

[Important]Important

When you deploy JMS endpoints in an OSGi bundle, the resulting endpoints are deployed as a JBI service unit.

For more information on using the OSGi packaging see Appendix D.

The elements used to configure JMS endpoints are defined in the http://servicemix.apache.org/jms/1.0 namespace. You will need to add a namespace declaration similar to the one in Example 1.2 to your xbeans.xml file's beans element.


In addition, you need to add the schema location to the Spring beans element's xsi:schemaLocation as shown in Example 1.3.