Java class loader and classpath considerations

Because WebSphere® eXtreme Scale stores Java™ objects in the cache by default, you must define classes on the classpath wherever the data is accessed.

Specifically, WebSphere eXtreme Scale client and container processes must include the classes or JAR files in the classpath when starting the process. When you are designing an application for use with eXtreme Scale, separate out any business logic from the persistent data objects.

See Class loading in the WebSphere Application Server documentation for more information.

For considerations within a Spring Framework setting, see the packaging section in the Spring framework overview.

For settings related to using the WebSphere eXtreme Scale instrumentation agent, see Entity performance instrumentation agent.

For details on adding your classes or JAR files to the stand-alone container server classpath, see startOgServer script (ORB) or startXsServer script (XIO).