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

Using GigaSpaces JMS Without Changing the Classpath

A JMS application may use the XAP RMI registry to a acquire its JMS resources. In this case the application administrator may prefer not to include the GigaSpaces JAR files in the application’s classpath. The GigaSpaces RMI registry specifies a Code Base where the application receives GigaSpaces’s class information automatically.

In order for an application to use XAP JMS without having to include XAP JAR files in the classpath the application administrator has to make sure that:

  1. The security policy contains:
grant {
    permission "", "";

For example, the security policy may be set to the policy file of GigaSpaces:<JSHOMEDIR>\policy\policy.all
  1. The security manager is set to be the RMISecurityManager: