This page describes an older version of the product. The latest stable version is 16.4.

JMS Messaging Support

XAP provide a JMS implementation, built on top of the core JavaSpaces layer. JMS messages are implemented as POJO, indexed, and routed to the relevant space partition according to the destination name. The XAP JMS implementation supports the unified messaging model, introduced in version 1.1 of the JMS specification.

Dependencies
In order to use this feature, include the ${XAP_HOME}/lib/optional/jms/xap-jms.jar file on your classpath or use maven dependencies:

<dependency>
    <groupId>org.gigaspaces</groupId>
    <artifactId>xap-jms</artifactId>
    <version>12.3.1</version>
</dependency>

See also:

For more information on dependencies, refer to Maven Artifacts.

Additional Resources

Best Practice	Description
Master-Worker Pattern	Grid computing pattern. Implementing distributed processing across multiple workers deployed into the Grid.
Priority Based Queue	Messaging based pattern. Can be used when moving from J2EE JMS Quality of Service into XAP.
Parallel Queue Pattern	Messaging based pattern. Can be used when moving from J2EE JMS Service Activator Aggregator Strategy/MDB into XAP.
Unit Of Work	Messaging based pattern. Can be used when moving from J2EE JMS Unit of Order into XAP.