here's the problem. Within a session, if an instance of Object1 is loaded and used, and then another Object2 is loaded, which has an Object1LightWeight, or Object1Proxy element, then the cache is hit and the original Object1 is found and assumed to be the right object. however, when it tries to return that object as either of the LightWeight, or Proxy classes, then it throws a classcast exception.



is this normal behavior? should hibernate not notice that these are different object types and go get the matching object?
We are using hibernate 2.0.2 on Jboss.
(if this has been fixed in a later version of hibernate.. that would be great :)))
Thnx
A.

This is normal and correct. You often need judicious use of evict() with the lightweight pattern.

thanks for the quick answer.. we rewrote the server side to use proxy classes rather then trying to keep track of what was loaded/where :)
Cheers
Ati.

is is possible for proxy and normal objects to conflict in the same way az with lightweight??
I had assumed that proxy would be the name as a full class except that a relationship is not loaded until accessed.. but we seem to be having mismatches between proxy/normal.

we are using hibernate 2.0.2... should we upgrade? have there been any changes in this behaviour since then?
Thnx