July 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6783) Using FetchType.EAGER with @ElementCollection results in multiple entity copies returned via Criteria query

by Greg Burcher (JIRA)

Using FetchType.EAGER with @ElementCollection results in multiple entity copies returned via Criteria query ----------------------------------------------------------------------------------------------------------- Key: HHH-6783 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6783 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.0 Environment: MySQL Reporter: Greg Burcher If we specify FetchType.EAGER on an @ElementCollection: @ElementCollection(fetch = FetchType.EAGER) @Column(name = "emailAddress") private Set<String> emailAddresses; then request all persisted objects of this class via Criteria: session.createCriteria(ReportSchedule.class).list(); The returned list contains multiple references to each ReportSchedule, one per email address. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

5
8
0 / 0

[Hibernate-JIRA] (BVAL-299) Add note on required Java version

by Gunnar Morling (JIRA)

13 years, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-7232) Hibernate ignores 'schema' attribute of @SequenceGenerator for Oracle sequences

by Scott Van Wart (JIRA)

Hibernate ignores 'schema' attribute of @SequenceGenerator for Oracle sequences ------------------------------------------------------------------------------- Key: HHH-7232 URL: https://hibernate.onjira.com/browse/HHH-7232 Project: Hibernate ORM Issue Type: Bug Components: annotations Affects Versions: 4.1.2 Environment: Hibernate 4.1.2.Final, Oracle 11gR2 Reporter: Scott Van Wart I wrote a mapping for a sequence such as: @SequenceGenerator( schema="jaseadm", name="applicantSignupSequence", sequenceName="seq_applicant_signup" ) And the generated SQL is as follows: DEBUG org.hibernate.SQL - select seq_applicant_signup.nextval from dual Which leads to this: WARN o.h.e.jdbc.spi.SqlExceptionHelper - SQL Error: 2289, SQLState: 42000 ERROR o.h.e.jdbc.spi.SqlExceptionHelper - ORA-02289: sequence does not exist -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
5
0 / 0

[Hibernate-JIRA] (BVAL-298) DefaultValidationProviderResolver should check context and current class loader for service file

by Hardy Ferentschik (JIRA)

13 years, 7 months

1
3
0 / 0

[Hibernate-JIRA] (HHH-7387) Integrate Draft 6 of the JPA 2.1 spec

by Steve Ebersole (JIRA)

13 years, 7 months

1
10
0 / 0

[Hibernate-JIRA] Created: (BVAL-216) Work with the JAXB EG to have a nice Bean Validation integration

by Emmanuel Bernard (JIRA)

Work with the JAXB EG to have a nice Bean Validation integration ---------------------------------------------------------------- Key: BVAL-216 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-216 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard -- 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

13 years, 7 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6896) Metamodel.managedType(...) implemented incorrectly

by Oliver Gierke (JIRA)

Metamodel.managedType(...) implemented incorrectly -------------------------------------------------- Key: HHH-6896 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6896 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.8 Reporter: Oliver Gierke Section 5.1.1 of the JPA specification defines {{Metamodel.managedType(...)}} as follows: {quote} Return the metamodel managed type representing the entity, mapped superclass, or embeddable class. {quote} Nevertheless the {{MetamodelImpl}} only considers entities, which clearly violates the spec. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6285) Exception when the entities has no @Id but just uses @EmbeddId

by Strong Liu (JIRA)

Exception when the entities has no @Id but just uses @EmbeddId -------------------------------------------------------------- Key: HHH-6285 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6285 Project: Hibernate Core Issue Type: Bug Reporter: Strong Liu Assignee: Hardy Ferentschik Fix For: 4.0.0.Beta1 Hardy, the logic of org.hibernate.metamodel.source.annotations.entity.ConfiguredClassHierarchy#determineDefaultAccessType is not correct ... as subject, if all entities use only @EmbeddId, then this method throws exception. we need find a better way to determin the default access type -- 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

13 years, 7 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-6911) Write DiscriminatorValue to DiscriminatorColumn when combined with InheritanceType#JOINED

by Steve Ebersole (JIRA)

Write DiscriminatorValue to DiscriminatorColumn when combined with InheritanceType#JOINED ----------------------------------------------------------------------------------------- Key: HHH-6911 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6911 Project: Hibernate Core Issue Type: Improvement Components: annotations, metamodel Reporter: Steve Ebersole Priority: Minor The JPA spec states that {{DiscriminatorColumn}} can be used in conjunction with JOINED inheritence. The only section that seems to deal with this combination is _11.1.10 DiscriminatorColumn Annotation_ where it says {quote} For the SINGLE_TABLE mapping strategy, and typically also for the JOINED strategy, the persistence provider will use a type discriminator column. The DiscriminatorColumn annotation is used to define the discriminator column for the SINGLE_TABLE and JOINED inheritance mapping strategies. {quote} Apparently this is meant to imply that even if providers do not need/use the discriminator for concrete class resolution (reading) they are still expected to write it out to the database. Dunno, thats just what we have been told :) Anyway, like I said, Hibernate itself does not need the discriminator column/value to interpret the concrete classes. However, in the interest of portability we certainly *could* write it out. Longer term -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

6
12
0 / 0

[Hibernate-JIRA] (HHH-7389) NullPointerException when use multi-tenancy and TableGenerator

by yujian (JIRA)

13 years, 7 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2012