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.
JMS basics and concepts.
JMS Messages with XAP
JMS messages implementation; supported and unsupported message types; message compression; accessing JMS messages via space API.
Creating JMS messages with the space API; reading/taking JMS messages with the space API; using JMS API with the MessageConverter to send custom POJOs to the space.
Including a JMS feeder in a processing unit using Spring JmsTemplate, and using the JMS message converter to send POJOs to the space, using the JMS API.
JNDI Overview, Binding/Obtaining ConnectionFactory and Destination instances.
JMS resources without JNDI
Obtaining JMS resources without JNDI, using JNDI with GSJMSAdmin.
Advanced options including transaction support and security.
|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.|