User development, A new message was posted in the thread "Inconsistent behaviour when fetching cached subclass entities?": http://community.jboss.org/message/527588#527588 Author : Jimmy Borg Profile : http://community.jboss.org/people/jborg Message: -------------------------------------------------------------- Hi all,   The use of jboss-cache as hibernate second-level cache is leading to inconsistent behaviour when fetching cached subclass entities as opposed to fetching non-cached subclass entities.   *Scenario* Consider a simple scenario having a parent entity:   and two subclass entities extending the above entity:     After persisting an instance of Subclass1 using:   Trying to fetch an instance of Subclass2 using:   will result in a +null+ return if the entity is not cached. This is the expected, correct behaviour.   However, when the entity with id +identifier1+ is cached, this will match and return an instance (of Subclass1) if the entity is cached. This appears to be both inconsistent behaviour, and a wrong result, as the entity with identifier +identifier1+ is of type Subclass1 not SubClass2, as requested in the call to em.find().   *Environment* jboss-cache 1.4.1.SP13 hibernate 3.2.5 jboss 4.2.2 -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/527588#527588