Product overview > Cache > Java object caching

Class loader and classpath considerations

Since eXtreme Scale stores Java objects in the cache by default, define classes on the classpath wherever the data is accessed.

Specifically, WXS client and container processes must include the classes or JARs in the classpath when starting the process. When designing an application for use with WXS, separate out any business logic from the persistent data objects.

See Class loading in the WAS ND information center for more information.

For considerations within a Spring Framework setting, see the packaging section in the Integrate with Spring framework topic.

For settings related to using the WebSphere eXtreme Scale instrumentation agent, see the Instrumentation agent topic.

Parent topic:

Java object caching concepts

Related concepts

Relationship management
Cache key considerations
Serialization performance
Insert data for different time zones


Search Tips   |   Advanced Search