October 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-606) Annotation Validation: @Immutable annotation does not throw error or warning on usage on subclass

by Paul Singleton Kossler (JIRA)

Annotation Validation: @Immutable annotation does not throw error or warning on usage on subclass -------------------------------------------------------------------------------------------------- Key: ANN-606 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-606 Project: Hibernate Annotations Issue Type: Bug Components: binder, documentation Affects Versions: 3.3.0.ga Environment: Hibernate3, Annotations.3.3.0 Reporter: Paul Singleton Kossler The @Immutable annotation does not throw a configuration error when used on a subclass. The action required depends upon the decision in a bug/patch request for adding mutable=false to subclasses. In the current rule set the Mapping Schema for pre annotations is leveraged to define the legallity of declaring a mapped object Immutable. Base/Root classes allowed, child classes of Mutable=true not allowed, in either case the mutability of an object is directly dependent upon the mutability of the root mapped object in the object hierarchy. The following documentation sources do not mention the issue in relation to the @Immutable annotation: * online/down-loadable Hibernate-Annotations * Java Persistence with Hibernate (ISBN: 1-932394-88-5) If the rules outlined above are accurate or not: A validation error or warning should be thrown from Configuration during the loading of an incorrectly mapped class. The current method is to check the Annotations at bind time, and only at the "correct" location. This meta-rule validation should occur during the binding of a mapping to the Configuration, quickly indicating an error. Using the "older" xml based mapping this occurs when the schema (xsd) validates the mapping file (xml). -- 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

16 years, 6 months

4
6
0 / 0

[Hibernate-JIRA] Created: (ANN-551) @SQLInsert. Columns in sql comes in different order depending on the application server used

by Søren Pedersen (JIRA)

@SQLInsert. Columns in sql comes in different order depending on the application server used -------------------------------------------------------------------------------------------- Key: ANN-551 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss 4.0.5. Oracle 10. Reporter: Søren Pedersen Problem: The columns in the sql you specify in SQLInsert annotation has be ordered in the same way hibernate sorts its properties when constructing the insert sql. Example: When WebLogic 9.2 is used the sql should look like this: "insert into acount (name, address, country) values (?,?,?)" But when JBoss 4.0.5 is used the sql should look like this: "insert into acount (address, country, name) values (?,?,?)" The above are only examples. Consequence: I have to have different SQLInsert's for every JEE apllication server we support, because the properties comes in different order depending on the application server used. Suggested solution: In the method org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements, PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final XClass annotatedClass, ExtendedMappings mappings) This property list shown below should be sorted to make sure that the properties also come in the same order: List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType ); -- 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

16 years, 6 months

4
8
0 / 0

[Hibernate-JIRA] Created: (ANN-665) @SQLInsert and @SQLUpdate doesn't parse given sql query to set parameters to PreparedStatement properly

by Gregory Klimov (JIRA)

@SQLInsert and @SQLUpdate doesn't parse given sql query to set parameters to PreparedStatement properly ------------------------------------------------------------------------------------------------------- Key: ANN-665 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-665 Project: Hibernate Annotations Issue Type: Bug Reporter: Gregory Klimov Priority: Minor Attachments: Employee.java According to ANN-551 sql parameters are set to PreparedStatement in pre-defined order which doesn't rely on sql query parameters definition (please refer to attached file). Developer should not be aware of internal hibernate implementation. -- 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

16 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-23) NotEmptyValidator throws ClassCastException on non-null wrapper types

by scott leberknight (JIRA)

NotEmptyValidator throws ClassCastException on non-null wrapper types --------------------------------------------------------------------- Key: HV-23 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-23 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 3.0.0.ga, Bundle 3.2.1 Reporter: scott leberknight Attachments: NotEmptyValidatorClassCastExceptionBugTest.java The NotEmptyValidator.isValid() method throws a ClassCastException if a non-null primitive wrapper type (e.g. Long) is supplied as the argument. The method assumes that if the value is not null, is not an array, collection, or map, that it can be cast to a String, which it cannot for primitive wrappers. See attached JUnit test, which also contains a possible fix to the logic and has a test for the fix too. I put the file in the org.hibernate.validator package so it can be dropped in as-is to the Hibernate Validator codebase. -- 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

16 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-217) Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported

by Michał Borowiecki (JIRA)

Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported ----------------------------------------------------------------------- Key: EJB-217 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-217 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.0.cr1 Environment: JBoss4.0.4.GA Reporter: Michał Borowiecki Having more than one relationship on en entity annotated with @OneToMany(fetch=FetchType.EAGER) causes exception when deploying the ejb3 module: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags. This bug is thoroughly explained here: http://www.jroller.com/page/eyallupu?entry=hibernate_exception_simultaneo... and depends on HHH-1718 "Have multiple bag fetches revert to subselect fetching for all but one of the bags" The temporary solution in HHH-1413 - disallowing multiple bag fetches is unsuitable to ejb3 environment, because the spec does not disallow it. -- 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

16 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-42) Check Hibernate Search deployment in JBoss AS 4.2

by Emmanuel Bernard (JIRA)

Check Hibernate Search deployment in JBoss AS 4.2 ------------------------------------------------- Key: HSEARCH-42 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-42 Project: Hibernate Search Issue Type: Task Reporter: Emmanuel Bernard Christian had issues when HSearch and core jars are in server/default/lib rather than the application scope Check that -- 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

16 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2878) LazyInitializationException - no session or session was closed

by Paul Andrews (JIRA)

LazyInitializationException - no session or session was closed -------------------------------------------------------------- Key: HHH-2878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2878 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate v 3.1.4-3.2.5, Oracle/HSQLDB/Whatever Reporter: Paul Andrews Attachments: testcase.zip A LazyInitializationException is thrown for a lazy set when the items in the set can be duplicates. This is manifested in a many-to-many implemented using join table; the session is still open but the session for the collection is set to null. The attached ZIP contains a test-case that demonstrates this. -- 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

16 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2884) Provide a sessionFactory close event or hook for the event listeners

by Emmanuel Bernard (JIRA)

Provide a sessionFactory close event or hook for the event listeners -------------------------------------------------------------------- Key: HHH-2884 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2884 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Fix For: 3.3 It can be done either: - as an event/eventListener - as a method that eventlisteners implement (symmetric of initialize()) The former being more flexible -- 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

16 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2863) testsuite fix-ups for maven and/or directory changes

by Steve Ebersole (JIRA)

testsuite fix-ups for maven and/or directory changes ---------------------------------------------------- Key: HHH-2863 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2863 Project: Hibernate3 Issue Type: Bug Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 -- 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

16 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2702) Officially move to JDK 1.4

by Steve Ebersole (JIRA)

Officially move to JDK 1.4 -------------------------- Key: HHH-2702 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2702 Project: Hibernate3 Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 This includes a number of considerations, such as (1) assuming JDBC3 as a baseline, (2) using the improved collections, etc. This will act as the grouping task for all JDK 1.4 migration tasks. -- 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

16 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2007