August 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5962) Custom POJO Loading strategy for cglib and javassist

by Ilya Samartsev (JIRA)

Custom POJO Loading strategy for cglib and javassist ---------------------------------------------------- Key: HHH-5962 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5962 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.1 Environment: Hibernate 3.6.1, PostgreSQL, OSGi Reporter: Ilya Samartsev I use hibernate in OSGi-enabled environment and have found a strange class-loading behaviour of the initializer proxies. The problem is that it's not possible to define simple domain-model OSGi bundles which have pojo-based classes to be enhanced by hibernate without importing org.hibernate.*, net.sf.cglib.proxy.*, javassist.util.proxy.*, etc. Testing environment: - A Model bundle with pojos and hibernate HBMs(they used by osgi-hibernate loader to enhance them). This bundle doesn't actually require any hibernate/cglib/javassist imports for the reason there are simple pojos in it. /src/com/example/TestPojoModel.java /META-INF/mappings/TestPojoModel.hbm.xml /META-INF/MANIFEST.MF Expected behaviour: To have "clean" bundle with pojos without any additional imports(e.g. org.hibernate.* or cglib/javassist). Enhance these classes without any errors. Current behaviour: These pojo-based model bundles require to import a lot of hibernate and cglib or javassist stuff to enhance these pojos. The problem is that hibernate uses the same classloader (from model bundle) to load both pojos and hibernate/codegeneration utility classes. Otherwise it crushes with ClassNotFoundException. Code explanation: Javassist ProxyFactory initialization: org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer: ProxyFactory factory = new ProxyFactory(); factory.setSuperclass( interfaces.length == 1 ? persistentClass : null ); factory.setInterfaces( interfaces ); factory.setFilter( FINALIZE_FILTER ); return factory.createClass(); How javassist loads classes by default: javassist.util.proxy.ProxyFactory: protected ClassLoader getClassLoader0() { ClassLoader loader = null; if (superClass != null && !superClass.getName().equals("java.lang.Object")) loader = superClass.getClassLoader(); else if (interfaces != null && interfaces.length > 0) ... } return loader; } It actually uses the classloader of the persistent class. My proposition: To create advanced classloader for ProxyFactory which has custom behaviour: 1. Firstly it tries to load class using the classloader of the persistent class 2. Secondly it tries to use the classloader of the curent hibernate bundle (which definitely has access to its own hibernate classes and imports the classes of the codegeneration libraries) final ClassLoader platformDelegatingClassLoader = new ClassLoader(persistentClass.getClassLoader()) { private final ClassLoader platformClassLoader = getClass().getClassLoader(); // on loadClass() it tries to use parent's classloader(parent = persistentClass.getClassLoader() - from the constructor) // if loadClass() didn't find class it tries to findClass() which is actually overridden to use current context's getClass().getClassLoader() @Override protected Class<?> findClass(String name) throws ClassNotFoundException { return platformClassLoader.loadClass(name); } }; ProxyFactory factory = new ProxyFactory() { @Override protected ClassLoader getClassLoader() { return platformDelegatingClassLoader; } }; -- 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

12 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3201) Provide osgi informations in hibernate MANIFEST.MF to be recognized as osgi-bundle

by Baptiste MATHUS (JIRA)

Provide osgi informations in hibernate MANIFEST.MF to be recognized as osgi-bundle ---------------------------------------------------------------------------------- Key: HHH-3201 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3201 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Reporter: Baptiste MATHUS Hi all, It would be great if the packaging of Hibernate could be done as osgi compatible jar. With little configuration, some plugins already exist to do it in simply. For informaiton, a jar can become osgi-compatible only by adding some properties inside the META-INF/MANIFEST.MF file. It lets the jar totally usable in a non-osgi environment, but let the jar be recognized as a "bundle" in an osgi-container (Eclipse, Apache Felix...). A good entrypoint for this, using maven2 to package, could be http://felix.apache.org/site/maven-bundle-plugin-bnd.html#MavenBundlePlug.... For example, Spring already did and their available jars on repo1.maven.org can be put directly in a eclipse/plugins directory and be recognized as a bundle/plugin. Cheers. -- 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

12 years, 4 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5812) OSGi support

by Rice Yeh (JIRA)

OSGi support ------------ Key: HHH-5812 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5812 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.6.0 Reporter: Rice Yeh Beacause OSGi framework is getting popular, many people need hibernate-core packaged as OSGi bundle. Although it is not hard for them to home-make a hibernate-core bundle, a bundle provided by hibernate team seems more portable and functional. Also, hibernate itself can use OSGi's features to enhance its functions. Rice -- 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

12 years, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6823) Short-name config values

by Steve Ebersole (JIRA)

Short-name config values ------------------------ Key: HHH-6823 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6823 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.1.0 The idea is to provide easier config as well as to isolate configurations from package moves as part of refactoring. * {{hibernate.transaction.jta.platform}} : Names the {{org.hibernate.service.jta.platform.spi.JtaPlatform}} to use. See {{org.hibernate.service.jta.platform.internal.JtaPlatformInitiator}}. For example, {{hibernate.transaction.jta.platform=JBossAS}} to name {{org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform}}; etc * {{hibernate.dialect}} : Names the {{org.hibernate.dialect.Dialect}} * TBC... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5689) Updated data remains in 2L Cache after rollback

by Nikita Koksharov (JIRA)

Updated data remains in 2L Cache after rollback ----------------------------------------------- Key: HHH-5689 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5689 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.6.0, 3.5.6 Reporter: Nikita Koksharov Attachments: UpdatedDataTest.java, UpdatedItem.java For entities with Transactional caching strategy, updated data remains in 2L cache after transaction rollback. Please look at testcase. -- 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

12 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] (HHH-7355) Hibernate criteria JOIN + additional condition (with clause) don't work with many-to-many association

by Steve Ebersole (JIRA)

12 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7355) Hibernate criteria JOIN + additional condition (with clause) don't work with many-to-many association

by Steve Ebersole (JIRA)

12 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7355) Hibernate criteria JOIN + additional condition (with clause) don't work with many-to-many association

by Artem Karpenko (JIRA)

12 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7355) Hibernate criteria JOIN + additional condition (with clause) don't work with many-to-many association

by Artem Karpenko (JIRA)

12 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] (OGM-218) Enable loading of collections thats been detached from session

by Ståle W. Pedersen (JIRA)

12 years, 5 months

3
15
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2012