I have discovered a strange case when trying to replicate a Hibernate 2nd level cache key on object update.

The cache key structure is like this:

cacheKey = {org.hibernate.cache.CacheKey}
|- key = {my.own.serializable.class}
|- type = {org.hibernate.type.ComponentType}
| |- typeScope = {org.hibernate.type.TypeFactory$TypeScopeImpl}
| | |- factory = {org.hibernate.impl.SessionFactoryImpl}
| |- propertyNames = {...}
| |- propertyTypes = {...}
| |- propertyNullability = {...}
| |- propertySpan = 2
| |- cascade = {...}
| |- joinedFetch = {...}
| |- isKey = true
| |- tuplizerMapping = {...}
|- entityOrRoleName = {java.lang.String} "my.Entity"
|- entityMode = {org.hibernate.EntityMode}
|- hashCode = 588688

The problem I can see here is that cacheKey.type.typeScope has a reference to my local SessionFactoryImpl which gets replicated over. Should typeScope (or one of its ancestors) not be declared as transient?

Looking at the o.h.t.ComponentType class I can see that typeScope attribute is not used at all in this class but only set in the constructor and kept in. Is this a Hibernate bug?

NOTE: ComponentType is used when the entity has a composite key and uses special identifier object for it.

We use Hibernate v3.6.7 and Ehcache v2.4.4.