January 2013 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3683) Embedded classes not taken into account when order_inserts is enabled

by Dave Stephan (JIRA)

Embedded classes not taken into account when order_inserts is enabled --------------------------------------------------------------------- Key: HHH-3683 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3683 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Reporter: Dave Stephan Attachments: EmbeddedClassTest.java It seems that Embedded classes are not being taken into account when batch insert statements are ordered. In the test case for example, when the insert statements are ordered (org.hibernate.engine.ActionQueue.sortInsertActions), the "state" of the Car EntityInsertAction is the (Embedded)Registration object, but the checkAction instance ,that should be indicating that there is a FK dependency, is of course, Driver. So the Car insert, which has a FK to the Driver insert, is ordered to execute before the Driver insert. -- 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

11 years, 2 months

3
4
0 / 0

[Hibernate-JIRA] (HHH-7910) Transaction timeout can cause non-threadsafe session access by reaper thread

by Brett Meyer (JIRA)

11 years, 2 months

5
28
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

11 years, 2 months

3
4
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

11 years, 2 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HBX-1100) hbm2dll creates FK constraint names that are too large for taget database dialect

by Duncan Keysell (JIRA)

hbm2dll creates FK constraint names that are too large for taget database dialect --------------------------------------------------------------------------------- Key: HBX-1100 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1100 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.4 Beta1 Reporter: Duncan Keysell When hbm2dll creates FK constraint names, it does so without following database resrictions. As hbm2dll knows it is using the Oracle10gDialect then it should not attempt to create FK constraint names that have more than 30 characters. With union-subclass mapping the pattern used by hbm2dll is to give a FK constraint an 18 character name on the class that directly has the association requiring the FK. If that class is subclassed the FK constraint added to the tables of the subclasses has 18+8n characters. Where n is the level of subclassing. Only two levels of subclassing are required before the constraint name exceeds 30 characters as below. I know it is possible to configure the initial name used for constraints using the foreign-key attribute in the mapping. However if I set that to 1 character then I still have a problem when 1 + 4*8 = 33. Therefore even using the foreign-key attribute I can only get 3 levels of subclassing. Shouldn't the algorithm to create FK names be aware of the 30 character limit, i.e be dialect aware. Couldn't it simply create a hashcode of the hashcode it currently creates and limit it to 30 characters (including the 'FK'). In the example below constraints of the lengths shown get added to each table for the many-to-one mapping with name="requestedNE": Class IACEndpointConfigElement (FK4C10C05A145A4B50) 18 chars IInterfaceConfigElement (FK4C10C05A145A4B50b6728c4a) 18 + 8 = 26 chars IFRvcConfigElement (FK4C10C05A145A4B50b6728c4ace4cc838) 18 + 8 + 8 = 34 chars ERROR Hibernate version: 3.2.2 Mapping documents: <class name="productSpecific.advancedAppInterfaces.attachmentCircuitService.IACEndpointConfigElement" table="IACEndpointConfigElement" abstract="true"> <many-to-one name="requestedNE" class="productSpecific.advancedAppInterfaces.attachmentCircuitService.IACServiceNEAssignmentConfigElement" column="requestedNE_ID" foreign-key="none" not-found="ignore" /> <union-subclass name="productSpecific.advancedAppInterfaces.attachmentCircuitService.IInterfaceConfigElement" table="IInterfaceConfigElement" abstract="false"> <union-subclass name="productSpecific.advancedAppInterfaces.attachmentCircuitService.IFRvcConfigElement" table="IFRvcConfigElement" abstract="false"> </union-subclass> </union-subclass> </class Code between sessionFactory.openSession() and session.close(): N/A Full stack trace of any exception that occurs: N/A Name and version of the database you are using: Oracle 10g The generated SQL (show_sql=true): [hibernatetool] 2008-11-26 09:56:40,000 DEBUG SchemaExport:303 - [hibernatetool] create table developer.IFRvcConfigElement ( [hibernatetool] INSTANCEID number(19,0) not null, [hibernatetool] oid varchar2(2048 char) not null, [hibernatetool] ReferenceKey varchar2(2048 char), [hibernatetool] InstanceName varchar2(255 char), [hibernatetool] InstanceDescription varchar2(255 char), [hibernatetool] requestedNE_ID number(19,0), [hibernatetool] ProtocolIFType number(10,0), [hibernatetool] InterfaceEncapType number(10,0), [hibernatetool] Dlci number(10,0), [hibernatetool] primary key (INSTANCEID) [hibernatetool] ); [hibernatetool] alter table developer.IFRvcConfigElement [hibernatetool] add constraint FK4C10C05A145A4B50b6728c4ace4cc838 [hibernatetool] foreign key (requestedNE_ID) [hibernatetool] references developer.IACSrvcNEAssgnmntCnfgElmnt; [hibernatetool] 2008-11-26 10:00:18,515 ERROR SchemaExport:274 - Unsuccessful: alter table developer.IFRvcConfigElement add constraint FK4C10C05A145A4B50b6728c4ace4cc838 foreign key (requestedNE_ID) references developer.IACSrvcNEAssgnmntCnfgElmnt [hibernatetool] 2008-11-26 10:00:18,515 ERROR SchemaExport:275 - ORA-00972: identifier is too long Debug level Hibernate log excerpt: DEBUG Problems with Session and transaction handling? N/A -- 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

11 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7002) SchemaExport ERROR when using in-memory database (H2) - drop constraint issue HHH000389

by andrea handevidt (JIRA)

SchemaExport ERROR when using in-memory database (H2) - drop constraint issue HHH000389 --------------------------------------------------------------------------------------- Key: HHH-7002 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-7002 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.0.1 Environment: H2Dialect, Hibernate 4.0 Reporter: andrea handevidt Priority: Minor Attachments: HibernateError.zip HHH-000389 resolved an issue with property name="hibernate.hbm2ddl.auto" value="create". It now performs a drop prior to create. When using an in-memory database this will throw errors on table with foreign key constraints. ERROR (SchemaExport:426) - HHH000389: Unsuccessful: alter table security_key drop constraint FK3031A4E0BE21E8D7 ERROR (SchemaExport:427) - Table "SECURITY_KEY" not found; SQL statement:alter table security_key drop constraint FK3031A4E0BE21E8D7 I noticed that the sqlDropString for org.hibernate.mapping.Table appends "if exists". This is missing for org.hibernate.mapping.ForeignKey. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

7
7
0 / 0

[Hibernate-JIRA] (HHH-7890) Quoting identifiers breaks @UniqueConstraint

by Sergey Parhomenko (JIRA)

11 years, 2 months

2
9
0 / 0

[Hibernate-JIRA] (HHH-7605) Provide details "An entity copy was already assigned to a different entity."

by Mattias Jiderhamn (JIRA)

11 years, 2 months

8
15
0 / 0

[Hibernate-JIRA] (HHH-7900) Add support for annotated many-to-many Map associations

by Brett Meyer (JIRA)

11 years, 2 months

1
6
0 / 0

[Hibernate-JIRA] Created: (HV-548) Validation annotation override in class inheritance

by Alex Landini (JIRA)

Validation annotation override in class inheritance --------------------------------------------------- Key: HV-548 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-548 Project: Hibernate Validator Issue Type: New Feature Components: annotation-processor Affects Versions: 4.2.0.Final Reporter: Alex Landini Hibernate validator should provide something like JPA @AttributeOverride to override parent class constraints. public class A { @Size(min = 1, max = 10) private String field1; @Min(2) private Integer field2; ... } @ConstraintOverrides({ @ConstraintOverride(name="field1", constraint={@Size(min=4, max =20)}), @ConstraintOverride(name="startDate", constraint={@Min(1)}) }) public class B extends A { ... } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2013