ActiveSpaces® Transactions uses these locations to resolve a class reference. The locations are searched in the following order:

The system CLASSPATH cannot be changed.

The contents of the deployment directories are then searched to resolve class resolutions as described in ActiveSpaces® Transactions Administration.

Finally the client's CLASSPATH is searched. All classes resolved using the client class path are sent over a network connection to the server. The client CLASSPATH is only available for class resolution if the detach option is set to false when the application was deployed.

	Client and server class paths are distinct. The client class path is never sent to the server. All resources in a client's class path that are in a shared file system visible to the server are still sent to the server from the client if the resource is not also in the server's class path.