After extracting the spring-core, spring-hibernate3 and all the various parts of Sakai, fixing the classloader issues surrounding IdGenerators etc, I find both Spring and Hibernate use CG Lib for proxies, and if you separate Spring from Hibernate, they fight over CGLib. Either Hibernate cant create proxies because it cant see the hibernate classes from CGLib or Spring cant get to CGLib because its not in shared. Looks like its not going to be possible to separate Spring and Hibernate into separate classloaders without providing some extra level of visibility between the classloaders.
T F D
Open Source Open Thought
Planet Apache
- Links for 2013-05-22
- JAX: Logging best practices
- JAX: Java performance myths
- Apache CXF 2.7.5 released
- What to look forward to at CamelOne, June 10-11th, 2013!
- Links for 2013-05-21
- Dynamic faceting with Lucene
- The intriguing theory of Expert Beginners
- JAX: Does parallel equal performant?
- Some benchmarking principles
Planet Sakai
- Does your Resources tool display the wrong file types?
- Right to Access Report Links and Upcoming Event
- MOOCs Explained: Radio Interview with University of Delaware
- California and the Right to Educational Access
- Byte-sized Site Info tool 14 May 2013
- Your personal WebLearn space
- The short and long of my trip to Anchorage
- Being Blackboard’s Sakai Chief Strategist – One Year In
- One More Day of Thought – Introducing CC-One (Formerly CC-Infinity)
- Marist College will help Lead the Sakai Open Academic Environment (OAE) Initiative
However, its now possible to switch the reflection library to javassist in H 3.2.5ga, you cant do it through the spring injected properties, but if you have a hibernate.properties in the class path containing, “hibernate.bytecode.provider=javassist” you can switch from CGLib to Javaassist just for hibernate…. but that now opens another problem, antlr, both Spring and Hibernate use Antlr… same problem different lib. Antlr is using the context classloader to do its work, but this is the shared classloader which cant see hibernate, so cant load anything. Since all of this is at startup, it may be worth looking at the proper separation between each Spring context so that the correct context classloader can be used.