May 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3799) PersistentSet does not honor hashcode/equals contract when loaded eagerly

by Igor Vaynberg (JIRA)

PersistentSet does not honor hashcode/equals contract when loaded eagerly ------------------------------------------------------------------------- Key: HHH-3799 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3799 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Igor Vaynberg Priority: Blocker Attachments: test.zip when persistent set is loaded eagerly in some situations it calls hashcode on its items before their field values are populated and then uses this incorrect hashcode to store them in the set. this makes set items inaccessible by any collection items that rely on hashcode such as contains(), remove(), etc. attached is a simple maven test project that reproduces the error, unzip and mvn test to run the test. -- 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, 5 months

16
58
0 / 0

[Hibernate-JIRA] Created: (HHH-4699) String mapped ENUMs can't be loaded from CHARs only VARCHARS (fix is trivial)

by Pierce Wetter (JIRA)

String mapped ENUMs can't be loaded from CHARs only VARCHARS (fix is trivial) ----------------------------------------------------------------------------- Key: HHH-4699 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4699 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5 Environment: all Reporter: Pierce Wetter An enum persisted as a string to a CHAR column comes back with extra spaces appended, so then fails the Enum.valueOf() lookup. Fix is easy: Line 132 of EnumType.java, method nullSafeGet, change: return Enum.valueOf( enumClass, name ); to return Enum.valueOf( enumClass, name.trim() ); Which should be perfectly logical, because spaces are illegal in enum names anyways. -- 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, 6 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HV-354) Improve message when building a ValidatorFactory but no provider is available in the classpath

by Emmanuel Bernard (JIRA)

Improve message when building a ValidatorFactory but no provider is available in the classpath ---------------------------------------------------------------------------------------------- Key: HV-354 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-354 Project: Hibernate Validator Issue Type: Improvement Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Priority: Minor Caused by: javax.validation.ValidationException: Unable to find a default provider at javax.validation.Validation $GenericBootstrapImpl.configure(Validation.java:264) at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:111) The exception message should be clearer than it is today something like "Found no Bean Validation provider: unable to create a ValidatorFactory. Add a provider like Hibernate Validator (RI) to your classpath." -- 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, 6 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HV-161) Hibernate Validator does not validate several groups in // during one navigation path

by Emmanuel Bernard (JIRA)

Hibernate Validator does not validate several groups in // during one navigation path ------------------------------------------------------------------------------------- Key: HV-161 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-161 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.0.0.Beta1 Reporter: Emmanuel Bernard Priority: Critical Fix For: 4.0.0.Beta2 -- 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, 6 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HV-445) Ensure meta models are completely unmodifiable

by Gunnar Morling (JIRA)

Ensure meta models are completely unmodifiable ---------------------------------------------- Key: HV-445 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-445 Project: Hibernate Validator Issue Type: Improvement Reporter: Gunnar Morling Fix For: 4.2.0.CR1 The internal meta model (BeanMetaDataImpl et al.) as well as the external one (BeanDescriptorImpl et al.) should be completely unmodifiable, as they could potentially be accessed from multiple threads at the same time. I made some more fields final/unmodifiable with HV-371, but there are some places left which I couldn't change easily and need some more consideration: * ConstraintDescriptorImpl#compositionType * ElementDescriptorImpl#constraintDescriptors * BeanMetaDatImpl#cascadedMembers (could be made unmodifiable after initialization instead of creating a new unmodifiable set with each call of getCascadedMembers() When looking through the model I found it quite complex to find out which collection fields are already unmodifiable and which not. I therefore thought about introducing a marker annotation @Unmodifiable which could be used to document unmodifiable fields. WDYT? -- 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, 6 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4962) @ManyToOne with @JoinTable fails

by Clint Popetz (JIRA)

@ManyToOne with @JoinTable fails -------------------------------- Key: HHH-4962 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4962 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.2 Reporter: Clint Popetz $ cat src/main/java/test/User.java package test; import javax.persistence.*; import org.hibernate.envers.Audited; import java.util.Set; The below code fails with "org.hibernate.MappingException: Unable to read the mapped by attribute for widgets in test.User!" but is supported by JPA, at least under hibernate. @Entity @Audited public class User { @Id private long id; @OneToMany(mappedBy="user") private Set<Widget> widgets; } $ cat src/main/java/test/Widget.java package test; import javax.persistence.*; import org.hibernate.envers.Audited; @Entity @Audited public class Widget { @Id private long id; @ManyToOne(fetch=FetchType.LAZY) @JoinTable(name = "widget_to_user", joinColumns = @JoinColumn(name = "widget_id"), inverseJoinColumns = @JoinColumn(name = "user_id")) private User user; } -- 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, 6 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6218) Bind @IdClass (multiple ids)

by Hardy Ferentschik (JIRA)

Bind @IdClass (multiple ids) ---------------------------- Key: HHH-6218 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6218 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- 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, 6 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-6262) Bind @EmbeddedId

by Hardy Ferentschik (JIRA)

Bind @EmbeddedId ---------------- Key: HHH-6262 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6262 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- 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, 6 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5291) Hibernate generates several join clauses for same table

by Igor Nikolaev (JIRA)

Hibernate generates several join clauses for same table ------------------------------------------------------- Key: HHH-5291 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5291 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Environment: Hibernate 3.5.2 Reporter: Igor Nikolaev Suppose you've got a mapping: <class name="Class" table="TABLE1" dynamic-update="true"> <id name="id" type="int"> <column name="ID" /> <generator class="assigned" /> </id> <discriminator column="CLASS_TYPE"/> <property name="property1" type="string" column="PROPERTY1" update="false" insert="false"/> <join table="TABLE2" optional="true"> <key column="ID" not-null="false"/> <property name="property2" column="PROPERTY2"/> </join> <subclass name="Subclass" discriminator-value="SUBCLASS"> <join table="TABLE2"> <key column="swift_id"/> <property name="property3" column="PROPERTY3"/> </join> </subclass> </class> As you can notice, we join the same table in subclass. Expected result is that Hibernat generates a query like this one: select this_.ID, this_.PROPERTY1, this_1_.PROPERTY2, this_1_.PROPERTY3 from TABLE1 this_ left inner join TABLE2 this_1_ on this_.ID=this_1_.ID Instead, Hibernate joins TABLE2 twice and generates the following query: select this_.ID, this_.PROPERTY1, this_1_.PROPERTY2, this_2_.PROPERTY3 from TABLE1 this_ left inner join TABLE2 this_1_ on this_.ID=this_1_.ID left outer join TABLE2 this_2_ on this_.ID=this_2_.ID -- 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, 6 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6271) deploying with a 1.0 orm.xml, gets unexpected error HHH00196:Error parsing XML (2) : cvc-complex-type.3.1: Value '1.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' ha

by Scott Marlow (JIRA)

deploying with a 1.0 orm.xml, gets unexpected error HHH00196:Error parsing XML (2) : cvc-complex-type.3.1: Value '1.0' of attribute 'version' of element 'entity-mappings' is not valid with respect to the corresponding attribute use. Attribute 'version' ha --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6271 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6271 Project: Hibernate Core Issue Type: Bug Components: entity-manager Reporter: Scott Marlow Fix For: 4.0.0.Beta1 -- 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, 6 months

4
19
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2011