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. GigaSpaces XAP JMS implementation supports the unified messaging model, introduced in version 1.1 of the JMS specification.
Starting with 10.1, the JMS support has been moved out of the core into its own jar files. When using JMS, please include the jar files located under
in your runtime configuration.
|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.