Program guide > (deprecated) Partitioning facility > Partitioning facility programming > Data partitioning patterns > Partition specific CMP data


Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.


Option A CMPs

This option is important for partitions with specific data access patterns. The problem with Option C Container-Managed Persistence (CMP)s with lifetime in cache is that WAS provides no API for removing such a CMP instance from the cache. WAS does provide a Java™ Message Service (JMS) mechanism that can remove an object, but this is not efficient for this scenario. So, objects cached using life time in cache cannot be removed programmatically from the cache by the application. This makes option C with lifetime cache unsuitable for partition data. The only option that will work is option A. Option A CMPs can be thought of as cached CMPs, although it is not technically a cache. The Java Platform, Enterprise Edition specification says that if an option A CMP method throws an unexpected exception then the bean instance must be removed from the container and the transaction currently active is rolled back. We will take advantage of this to implement the partition data cache.


Parent topic:

Partition specific CMP data


Related concepts

Partition specific CMP data