[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4786?page=c...
]
Steve Ebersole commented on HHH-4786:
-------------------------------------
The really tricky part is that in some cases you'd want to prefer the "system
classloader" (java/javax classes) and the "tccl" in others (custom
Serializable impls).
SerializableType + custom Serializable class + L2 cache causes
problems
-----------------------------------------------------------------------
Key: HHH-4786
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4786
Project: Hibernate Core
Issue Type: Bug
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.5.0-Beta-3
The changes done for HHH-2990 cause an issue when users map non-JDK Serializable classes
using SerializableType in combination with attempting to cache those values into second
level cache.
SerializableType reports the classloader to use for deserialization as the classloader of
java.io.Serializable (which is generally null indicating the "bootstrap class
loader"). However that classloader will (generally) not have visibility into the
classloader needed to see these non-JDK classes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira