JCache and HazelcastInstance ownership

The provider is explicit, not SPI-discovered

The module’s META-INF/services/javax.cache.spi.CachingProvider file contains no provider class. HazelcastJCaching.cacheManagerOf constructs HazelcastCachingProvider and passes the connected instance through propertiesByInstanceItself(hazelcastInstance).

val manager = HazelcastJCaching.cacheManagerOf(hazelcast)
val users = HazelcastJCaching.getOrCreate<String, User>(
    hazelcastInstance = hazelcast,
    name = "users-v1",
    configuration = MutableConfiguration<String, User>().apply {
        setTypes(String::class.java, User::class.java)
    },
)

Do not assume that Hazelcast is the default provider on the classpath. This factory path explicitly selects the supplied Hazelcast instance even when the application uses multiple JCache providers.

Cache identity includes the cluster and name

getOrCreate looks up a cache by name and creates it from the configuration only when absent. Reusing a name in one cluster shares distributed data with every component using that name. Include a domain and schema generation in the name.

MutableConfiguration.setTypes makes the typed JCache contract explicit but does not define Hazelcast wire serialization. Configure serializers and schema compatibility at the cluster boundary.

Separate proxy, data, and instance lifecycle

HazelcastJCaching receives an externally owned HazelcastInstance; the module source never calls shutdown(). Closing a cache or manager is separate from shutting down the client or member.

try {
    users.put("42", user)
} finally {
    users.close()
    // The application lifecycle owner closes hazelcast later.
}

Near-cache close also removes only its listener and L1. It neither destroys the IMap nor shuts down Hazelcast. Keep deployment shutdown, proxy close, and distributed-data deletion as separate actions.

Sources and tests

• HazelcastJCaching.kt
• HazelcastCaches.kt
• CachingProvider service resource
• HazelcastCachesTest.kt