July 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-389) Support conditional validation at property level

by jason shi (JIRA)

Support conditional validation at property level ------------------------------------------------ Key: HV-389 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-389 Project: Hibernate Validator Issue Type: New Feature Components: engine Affects Versions: 4.1.0.Final Reporter: jason shi Assignee: Hardy Ferentschik In Oval, there is a "when" attribute in each ConstrainsChecker,which can be used for conditional check. In the following example fieldB must not be null only if fieldA is not null as well. With the prefix groovy: it is indicated that the formula is expressed in the Groovy language. {code} public class BusinessObject { private String fieldA; @NotNull(when = "groovy:_this.fieldA != null") private String fieldB; } {code} Although we can use ScriptAssert as a work-around, but ScriptAssert can't be used at property level validation, and the "when" attribute make the validation logical more clearly. In UI layer validation, this feature is very important in instant UI validation. The hibernate validator should have the ability to pass a ValueContext to the Validator,then we can write a custom Contrains to implement this feature. -- 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, 8 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HBX-1081) Generation of meta attributes for composite-id

by Anders Reinhardt Hansen (JIRA)

Generation of meta attributes for composite-id ---------------------------------------------- Key: HBX-1081 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1081 Project: Hibernate Tools Issue Type: Improvement Components: reverse-engineer Affects Versions: 3.2.beta11 Environment: All, not related to platform. Reporter: Anders Reinhardt Hansen Priority: Minor The ReverseEngineeringStrategy has a method; "public Map tableToMetaAttributes(TableIdentifier tableIdentifier)" This method returns a Map of meta tags which will be put inside the class node of the hbm files that are generated. It would be a nice addition if we could have a method like this which placed meta tags inside the composite id node. the method could be called "public Map tableToMetaAttributesForCompositeId(TableIdentifier tableIdentifier)" An example of the problem is shown in the below example; <class name="XXX1" table="XXX1"> <meta attribute="generated-class">XXX1Base</meta>  <composite-id name="XXX2" class="XXX2"> <meta attribute="generated-class">XXX2Base</meta>  <key-property name="propertyXXX" type="int"> <column name="ColoumnXXX" /> </key-property> <key-property name="YYY" type="int"> <column name="ColoumnYYY" /> </key-property> </composite-id> ... </class> The issue was discussed on the forum in topic http://forum.hibernate.org/viewtopic.php?t=989476 -- 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, 8 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6501) Support @org.hibernate.annotations.Parent

by Hardy Ferentschik (JIRA)

Support @org.hibernate.annotations.Parent ----------------------------------------- Key: HHH-6501 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6501 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6393) Implement attribute overrides for embeddables

by Hardy Ferentschik (JIRA)

Implement attribute overrides for embeddables --------------------------------------------- Key: HHH-6393 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6393 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

14 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6486) Negative ID created using Sequences

by Andreas Beckers (JIRA)

Negative ID created using Sequences ----------------------------------- Key: HHH-6486 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6486 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.Beta4, 4.0.0.Beta1 Environment: JBoss 7.0.0.Final with Hibernate 4.0.0.Beta4, Oracle 10 Express Reporter: Andreas Beckers We use seperated sequences for each table. Our IDs are annotated like this: @SequenceGenerator(name = "PersonGen", sequenceName = "person_id_seq") @Id @GeneratedValue(generator = "PersonGen") public long getId() { return _id; } The sequence is defined like this: CREATE SEQUENCE person_id_seq START WITH 1 INCREMENT BY 1 NOCACHE; The Problem is, that I get negative IDs in my object and the generated IDs are not unique. I get the error java.sql.SQLIntegrityConstraintViolationException: ORA-00001: Unique Constraint (VESUVZPONF.PERSON_PKEY) verletzt In the log I see: Generated identifier: -21, using strategy: org.hibernate.id.enhanced.SequenceStyleGenerator The code worked in JBoss 6.0.0.Final using Hibernate 3.6.0.Final I tried auto strategy which uses a single sequence that works fine. There are ManyToOne and OneToMany relations with cascade all, don't know if that's of importance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (OGM-63) Remove unused code branches and unnecessary null checks

by Juraci Paixao Krohling (JIRA)

Remove unused code branches and unnecessary null checks ------------------------------------------------------- Key: OGM-63 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-63 Project: Hibernate OGM Issue Type: Improvement Components: core Affects Versions: 3.0.0.Alpha1 Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Fix For: 3.0-next I ran the FindBugs code analysis tool and noticed that there are some unnecessary null checks and unused code branches in Hibernate OGM Core module, like the following example from OgmLoader: {code:title=OgmLoader.java} //we don't load more than one instance per row, shortcircuiting it for the moment final int[] collectionOwners = null; for ( int i=0; i<collectionPersisters.length; i++ ) { final CollectionAliases[] descriptors = getCollectionAliases(); final boolean hasCollectionOwners = collectionOwners !=null && collectionOwners[i] > -1; //true if this is a query and we are loading multiple instances of the same collection role //otherwise this is a CollectionInitializer and we are loading up a single collection or batch final Object owner = hasCollectionOwners ? row[ collectionOwners[i] ] : null; //if null, owner will be retrieved from session final CollectionPersister collectionPersister = collectionPersisters[i]; final Serializable key; if ( owner == null ) { key = null; } else { key = collectionPersister.getCollectionType().getKeyOfOwner( owner, session ); //TODO: old version did not require hashmap lookup: //keys[collectionOwner].getIdentifier() } readCollectionElement( owner, key, collectionPersister, descriptors[i], resultSet, //TODO CURRENT must use the same instance across all calls session ); {code} Note that {{collectionOwners}} is always {{null}}. Thus, {{hasCollectionOwners}} is always {{false}}, causing {{owner}} to always be {{null}}. Then, the {{if ( owner == null ) }} will always be evaluated as true, turning the else part to be unnecessary. The above code can be rewritten as: {code:title=OgmLoader.java} final CollectionAliases[] descriptors = getCollectionAliases(); // this line was inside the for loop... it seems it can be outside for ( int i=0; i<collectionPersisters.length; i++ ) { final CollectionPersister collectionPersister = collectionPersisters[i]; readCollectionElement( null, null, collectionPersister, descriptors[i], resultSet, //TODO CURRENT must use the same instance across all calls session ); } {code} This JIRA is to track similar issues to the example above. -- 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, 8 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-740) TimeoutTest and ClasstypeFieldCacheExtractionTest

by Hardy Ferentschik (JIRA)

TimeoutTest and ClasstypeFieldCacheExtractionTest ------------------------------------------------- Key: HSEARCH-740 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-740 Project: Hibernate Search Issue Type: Bug Components: build, tests Affects Versions: 3.4.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0 * _TimeoutTest_ uses query timeouts which are not available via the postgres jdbc driver (see also JBPAPP-2945) * _ClasstypeFieldCacheExtractionTest_ does not properly close a transaction -- 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, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-780) Dirty analysis of @IndexedEmbedded on a superclass collection fails

by Samppa Saarela (JIRA)

Dirty analysis of @IndexedEmbedded on a superclass collection fails ------------------------------------------------------------------- Key: HSEARCH-780 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-780 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.4.0.Final Reporter: Samppa Saarela AbstractDocumentBuilder.indexedEmbeddedCollectionRoles contains roles that are bound to given indexed class (e.g. ASubclass.commonCollection). In Hibernate collection roles are bound to the class they are defined in (e.g. ASuperclass.commonCollection). Given this mismatch the collection gets excluded from being indexed in FullTextIndexEventListener.processCollectionEvent > AbstractDocumentBuilder.isCollectionRoleExcluded. In the test case (in github pull request) this bug is reproduced using an abstract superclass, but I suspect it affects also other kind of indexed hierarchies. -- 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, 8 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-772) Isolate JGroups tests to be able to run different test profiles in parallel

by Sanne Grinovero (JIRA)

Isolate JGroups tests to be able to run different test profiles in parallel --------------------------------------------------------------------------- Key: HSEARCH-772 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-772 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero When running the full testsuite on CI, each profile is executed in parallel in separate workspaces and using each it's own database. Still it seems that JGroups occasionally forms clusters among the different runnin testsuites, causing many failures. -- 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, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-739) Define an M2Eclipse configuration section in the parent pom.xml

by Sanne Grinovero (JIRA)

Define an M2Eclipse configuration section in the parent pom.xml --------------------------------------------------------------- Key: HSEARCH-739 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-739 Project: Hibernate Search Issue Type: Task Components: build Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 3.5 Recent versions of M2 require this configuration, or the project won't build out of the box. -- 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, 8 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 July 2011