March 2013 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (BVAL-434) Clarify exception type if cross-parameter validator support neither Object nor Object[]

by Gunnar Morling (JIRA)

12 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] (BVTCK-42) More assertions for BV 1.1

by Gunnar Morling (JIRA)

12 years, 9 months

3
15
0 / 0

[Hibernate-JIRA] (HHH-8057) Bad proxy behavior when using store_data_at_delete and audited parent/child relationships

by Adar Dembo (JIRA)

12 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] (HV-744) Wrap exceptions from message interpolator into ValidationException

by Gunnar Morling (JIRA)

12 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] (HV-743) Messages using EL should stay unchanged also if RuntimeExceptions are raised

by Gunnar Morling (JIRA)

12 years, 9 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HHH-6496) ClassCastException inside proxy without explicit casting in application code

by Joseph Calzaretta (JIRA)

ClassCastException inside proxy without explicit casting in application code ---------------------------------------------------------------------------- Key: HHH-6496 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6496 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.6 Environment: Hibernate version 3.6.6 database-independent JDK 1.6 Windows 7 and Linux CGLib and javassist Reporter: Joseph Calzaretta Attachments: ProxySubclassExample.zip Noticed that an lazily-loaded entity was getting a ClassCastException inside the proxy method without any explicit casting in the application code. I've pared down the issue to a minimal example and attached a FunctionalTestCase. See: {code:title=BaseClass.java} public abstract class BaseClass { public abstract SubClass toSubClass(); } {code} {code:title=SubClass.java} public class SubClass extends BaseClass { public Subclass toSubClass() { return this; } } {code} {code:title=ProxySubclassTest.java} public void testProxySubclass() throws Exception { s = this.openSession(); tx = s.beginTransaction(); LazyReferenceToBaseClass lazyReferenceToBaseClass = (LazyReferenceToBaseClass) s.load(LazyReferenceToBaseClass.class, lazyReferenceToBaseClassId); BaseClass baseClass = lazyReferenceToBaseClass.getBaseClass(); SubClass subClass = baseClass.toSubClass(); // Throws // java.lang.ClassCastException: BaseClass_$$_javassist_1 cannot be cast to SubClass // at BaseClass_$$_javassist_1.toSubClass(BaseClass_$$_javassist_1.java) } {code} This is clearly related to "the dreaded proxy problem" with its variety of solutions/workarounds(http://community.jboss.org/wiki/ProxyVisitorPattern) but in those cases the application code makes a mistaken assumption that it can downcast a proxy. In this example, there is no explicit downcasting, although I suppose SubClass.toSubClass() could be considered "implicit downcasting". Within SubClass, "this" must refer to an instance of SubClass, and it presumably should be returnable as such. I haven't checked what's going on in the proxy code, but I presume that it sees that it is trying to return the item corresponding to the proxy itself, and attempts to return that proxy. However the proxy is not an instance of SubClass and there is a ClassCastException. I'd suggest one of the following solutions: - have the proxy return the unproxied (already initialized) object if it cannot cast it appropriately - have the proxy re-proxy the already initialized object into an instance of the appropriate class - have some explicit documentation as to why this cannot be expected to work and why domain classes need to avoid this behavior. In any case it seems poor that even improperly written entity code can cause an exception inside the proxy-specific code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] (HHH-8058) Querying property-level revisions

by Alin Iacob (JIRA)

12 years, 9 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2054) Persistent wrapper collections should support generics

by Daniel Kandel (JIRA)

Persistent wrapper collections should support generics ------------------------------------------------------ Key: HHH-2054 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2054 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr2 Reporter: Daniel Kandel Hibernate persistent wrapper collections - classes that extend AbstractPersistentCollection and implement map, set or list (like PersistentSet and PersistentList), should support generics (PersistentSet<String>, PersistentMap<Integer, String>). In order to create a custom collection, one must extend one of these classes, but then the new collection cannot support generics. -- 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, 9 months

4
4
0 / 0

[Hibernate-JIRA] (HHH-8051) targetAuditMode=RelationTargetAuditMode.NOT_AUDITED should allow for missing entity targets

by Adar Dembo (JIRA)

12 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] (HV-742) Spring Bean validation fails when method is generic

by Timothy Pote (JIRA)

12 years, 9 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2013