Book-Buyer Example Release Notes

What's Important

• space-examples.jar
  This file contains all the client class files needed to run the JSTK examples, and should be in the CLASSPATH of the clients.

• space-examples-dl.jar
  This file contains all the class files that services and other clients will need to interact with the clients from the examples. The java.rmi.server.codebase property of the clients should be a URL that points to this file. If the codebase property is set correctly, this file will be downloaded to the space and therefore will not need to be in its CLASSPATH.

System Properties

Several properties control the behavior of book-buyer example clients:

java.security.policy

The security policy file the client should use. This should be the policy file in the books example directory.

java.rmi.server.codebase

A URL from which the space can download any necessary classes. If you are using the provided jar files, this property should specify a URL that includes the space-examples-dl.jar file.

com.sun.jini.use.registry

If the com.sun.jini.use.registry property is set to a non-null value, the client will look for the necessary services in the RMI registry. If it is not set, or set to null, the client will look for the necessary services using the Jini^TM Lookup service.

Note: The JSTK examples can be run using only an RMI registry or both an RMI registry and a Jini Lookup service. Currently, an RMI registry has to be running for the clients to locate each other, even if Jini Lookup services are also being used to get references to a space and transaction manager. The JSTK examples may be modified in a future release to have the ability to use only Jini Lookup services.

com.sun.jini.rmiRegistryPort

This property can be used to set the port on which the client will look for the registry. If this property is not set, a value of 1099 is used.

outrigger.spacename

The name that the example clients will use to try to find a net.jini.space.JavaSpace. If looking in an RMI registry, the value of this property will be the name that will be used for the lookup call. If using a Jini Lookup service, the client will look for a service with a net.jini.lookup.entry.Name attribute set to the value of this property.

com.sun.jini.lookup.groups

If using Jini Lookup services, this property specifies which lookup groups to use. The value of this property is one or more strings, separated by commas or white space. If there is any white space in the list, the entire list must be enclosed in double quotes. The string "public" will converted to "" (the empty string). If no group list is provided, it will default to the single entry list {""}. If the list consists only of the string, "none", the client will not use groups to find the lookup service.

com.sun.jini.lookup.locator

If using Jini Lookup servers, this property can be used to specify a specific lookup server. The value of this property should be a Jini-formatted URL (jini://hostname[:port]). If this property is not set, the client will default to using groups. The preferred method of locating a lookup service is by using the com.sun.jini.lookup.groups property, described above.

Known Bugs

Currently, there are no known outstanding bugs in the JSTK 1.0 version of the books example.

What's New

Significant changes from 1.0Beta:

• Lookup Service Selection Simplified
  In the 1.0Beta release of Outrigger, selection of lookup services (RMI registry vs. Jini Lookup service) was performed by setting two properties to specified class names. Now it is controlled by the single com.sun.jini.use.registry property, as described above.

• New Jar File Structure
  The 1.0Beta release of Outrigger stored all its class files in a single zip file. This effectively disabled code downloading. For this release, the example classes have been separated into two jar files, as described earlier in this document.

• Shutdown and Delete Buttons Removed from Watcher Client
  In the 1.0Beta release of Outrigger, the watcher client had a button to "shutdown" the JavaSpaces service in order to test the ShutDownAdmin interface. Because this interface has been removed, the Shutdown button has been removed as well.

  Also in the 1.0Beta release of Outrigger, the watcher client had a button that allowed the user to delete a specific entry listed in the entry-list pane. Changes to the AdminIterator made the Delete button no longer applicable.