July 2007 - hibernate-issues - Jboss List Archives

[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: (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-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

[Hibernate-JIRA] Created: (HHH-2704) Migrate to Maven2 for build

by Steve Ebersole (JIRA)

Migrate to Maven2 for build --------------------------- Key: HHH-2704 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2704 Project: Hibernate3 Issue Type: Task Components: build Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 This is the *official* move to Maven2 issue (since I'm the only one willing to actually do 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

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2555) Create new RegionFactory for JBossCache

by Steve Ebersole (JIRA)

Create new RegionFactory for JBossCache --------------------------------------- Key: HHH-2555 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2555 Project: Hibernate3 Issue Type: New Feature Components: caching (L2) Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 Based on discussions ongoing between the Hibernate and JBossCache teams, create a new RegionFactory which takes fulfills the discussed requirements. These requirements are spread throughout: (1) JBC wiki : http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernateAlignment (2) email thread : http://www.mail-archive.com/hibernate-dev%40lists.jboss.org/msg01055.html (plus a few others referenced within the above resources). -- 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
3
0 / 0

[Hibernate-JIRA] Created: (ANN-607) The source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution.

by Steve Gilbert (JIRA)

The source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution. ------------------------------------------------------------------------------------------- Key: ANN-607 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-607 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.3. Reporter: Steve Gilbert As noted in the summary, the source for hibernate-commons-annotations is not packaged with the 3.3.0 GA distibution. -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2617) Warning on tables with inheritance when table defaults are set in entity-mappings

by Stephen Todd (JIRA)

Warning on tables with inheritance when table defaults are set in entity-mappings --------------------------------------------------------------------------------- Key: HHH-2617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2617 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.2 Environment: Using Annotations Reporter: Stephen Todd Priority: Trivial Attachments: inheritance-orm.xml, TestSingleTableInheritanceWarnings.java The following warning message is logged when entity-mapping defaults are set and tables with inheritance are present: Illegal use of @Table in a subclass of a SINGLE_TABLE hierarchy: class.name.Here I attached a test case that recreates the problem. Basically, the error occurs when a resource contains persistence-unit-defaults. It appears that hibernate creates an @Table attribute for every registered entity when I think it should only do it for non-single table inheritance entities. Below is an example of the orm.xml <entity-mappings> <persistence-unit-metadata> <persistence-unit-defaults> <catalog>public</catalog> </persistence-unit-defaults> </persistence-unit-metadata> <entity class="hibernatebugs.TestAnnotationWarnings$ParentEntity"> <inheritance strategy="SINGLE_TABLE"/> </entity> </entity-mappings> Test requires EasyMock and Log4J. -- 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
6
0 / 0

[Hibernate-JIRA] Created: (ANN-610) Copy/paste errors in reference docs

by Christian Bauer (JIRA)

Copy/paste errors in reference docs ----------------------------------- Key: ANN-610 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-610 Project: Hibernate Annotations Issue Type: Bug Components: documentation Reporter: Christian Bauer Priority: Minor The section on bidirectional indexed collections has copy/paste errors. Also, show a List example and drop the map-key example. -- 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
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007