April 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-452) Incorrect Paths when using fluent API to add constraints to a context

by Glen Hilton (JIRA)

Incorrect Paths when using fluent API to add constraints to a context --------------------------------------------------------------------- Key: HV-452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-452 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Beta2, 4.2.0.Beta1 Reporter: Glen Hilton The bug actually should be found by existing test cases in ConstraintValidatorContextTest, but there happens to be a bug there too. First to the test case bug: In ConstraintValidatorContextTest, within the testing utility method assertMessageAndPath there's a call to TestUtil.assertEqualPaths. TestUtil.assertEqualPaths doesn't assert anything it returns a boolean, this fact causes line 156: {{assertEqualPaths( messageAndPath.getPath(), PathImpl.createPathFromString( expectedPath ) );}} to not actually test anything. Given this testing bug, we don't know that ConstraintValidatorContextTest.testMultipleMessages line 144: {{assertMessageAndPath( messageAndPathList.get( 1 ), message2, "" );}} should actually fail. As a quick and dirty fix to the test cases, we could wrap the existing line 144 with assertTrue, so it would end up: {{assertTrue(assertMessageAndPath( messageAndPathList.get( 1 ), message2, "" ))}} Now two of the tests in ConstraintValidatorContextTest will fail. These test cases appear to fail because within ConstraintValidatorContextImpl, all of the subclasses (ErrorBuilderImpl, NodeBuilderImpl, InIterableNodeBuilderImpl) are getting instantiated with a reference to the propertyPath at the "base" level (ConstraintValidatorContextImpl.propertyPath). Meaning when the subclasses update the propertyPath they are actually all updating the same underlying object, leading to incorrect paths being created. This bug appears to have been introduced with HV-395 as before there was code to create a copy of the path when ErrorBuilderImpl.addNode was called. Sorry I don't have an actual fix to provide, as I don't fully grasp HV-395. p.s. thanks for all the hard work! -- 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

14 years, 11 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-6130) Exception when declare alias for Property

by Senthilkumar Arumugam (JIRA)

Exception when declare alias for Property ----------------------------------------- Key: HHH-6130 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6130 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Senthilkumar Arumugam Priority: Blocker The query throws Exception with the message "Caused by: org.hibernate.QueryException: , expected in SELECT [SELECT s.id AS id, s.status AS status, s.firstName AS companyName FROM Student AS s ORDER BY s.firstName asc]" when I declare aliases for the properties. The query executes fine when I do not have aliases for any property in the query. -- 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

14 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-879) Enable joining the same association twice with Criteria

by Simon Oualid (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-879?page=co... ] Simon Oualid commented on HHH-879: ---------------------------------- Simplest workaround I found : {code} Restrictions.sqlRestriction( " exists ( select null from BaseEntity be2, ChildEntity ce1, ChildEntity ce2 " + "where be2.id = baseentity1_.id and ce1.id_parent = be2.id and ce2.id_parent = be2.id " + "and ce1.id = "+ firstEntityId +" and ce2.id = "+ secondEntityId +") " ); baseEntityCriteria.add( r ); {code} Regards. > Enable joining the same association twice with Criteria > ------------------------------------------------------- > > Key: HHH-879 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-879 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Vladimir Bayanov > > Make double joining the same association with Criteria.createCriteria possible. See: http://forum.hibernate.org/viewtopic.php?t=931249 -- 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

14 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3008) Cascade delete does not work with unidirectional @OneToMany and @JoinTable

by Daniel Dyer (JIRA)

Cascade delete does not work with unidirectional @OneToMany and @JoinTable -------------------------------------------------------------------------- Key: HHH-3008 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3008 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Standalone entity manager (JavaSE 5.0). H2 database. Reporter: Daniel Dyer A unidirectional one-to-many relationship defined as follows: public class Owner { @OneToMany(cascade = CascadeType.ALL) @JoinTable(name = "owner_element", joinColumns = @JoinColumn(name = "owner_id", nullable = false, updatable = false), inverseJoinColumns = @JoinColumn(name = "element_id", nullable = false, updatable = false)) private List<Element> elements; // ... } Attempting to delete an instance of Owner should also delete all associated instances of Element. Instead I get the following error: SEVERE: Referential integrity constraint violation: FK56BBF9C487E817D: PUBLIC.OWNER_ELEMENT FOREIGN KEY(OWNER_ID) REFERENCES PUBLIC.OWNER(ID) [23003-63] This is because Hibernate attempts to delete the Owner row without first removing the rows from the join table. -- 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

14 years, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (OGM-49) A new node is unable to join a running cluster

by Sanne Grinovero (JIRA)

A new node is unable to join a running cluster ---------------------------------------------- Key: OGM-49 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-49 Project: Hibernate OGM Issue Type: Bug Reporter: Sanne Grinovero Assignee: Sanne Grinovero When a new node containing no data is joining a cluster which already owns some persistent entities, state transfer errors are generated and the join fails if the existing caches had not initialized all involved caches (for example if nothing was ever stored in the IDENTIFIERS cache). The join can tolerate this errors by changing the configuration to use strictPeerToPeer=false, and we can also make sure that all caches are always initialized at startup. -- 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

14 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6129) org.hibernate.LobHelper#createNClob can now return NClob

by Steve Ebersole (JIRA)

org.hibernate.LobHelper#createNClob can now return NClob -------------------------------------------------------- Key: HHH-6129 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6129 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 Since 4.0 will base on JDK 1.6, we can return java.sql.NClob from org.hibernate.LobHelper#createNClob -- 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

14 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6128) Create simplier LobCreator from Session

by Steve Ebersole (JIRA)

Create simplier LobCreator from Session ---------------------------------------- Key: HHH-6128 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6128 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 {{Session.getLobCreator()...}} -- 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

14 years, 11 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5914) Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals

by Gail Badner (JIRA)

Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals ----------------------------------------------------------------------------------- Key: HHH-5914 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5914 Project: Hibernate Core Issue Type: Improvement Components: core, documentation Reporter: Gail Badner Fix For: 4.0.0.Alpha3 Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals. Manuals should refer to constants in org.hibernate.type.StandardBasicTypes instead. -- 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

14 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4722) Proxy initialization should be fail-fast when accidentially initializing from event listeners or interceptor

by Joonas Koivunen (JIRA)

Proxy initialization should be fail-fast when accidentially initializing from event listeners or interceptor ------------------------------------------------------------------------------------------------------------ Key: HHH-4722 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4722 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Hibernate 3.2.2 Reporter: Joonas Koivunen Proxy initialization done in event listeners (at least post-update) with an entity that has a mapped collection seems to result in {code}org.hibernate.AssertionFailure: collection [role-of-collection] was not processed by flush(){code} at flush time. By googling up problems like the above assertion failure seems that other people than me have spent quite a time searching for the origin of this problem; for me it was using a toString() of an uninitialized proxy. -- 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

14 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-447) Create documentation for boolean composition of composing constraints

by Hardy Ferentschik (JIRA)

Create documentation for boolean composition of composing constraints --------------------------------------------------------------------- Key: HV-447 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-447 Project: Hibernate Validator Issue Type: Bug Components: documentation Reporter: Hardy Ferentschik Fix For: 4.2.0.CR1 Seems we forgot the online docs for HV-390 -- 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

14 years, 11 months

2
3
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 April 2011