September 2011 - hibernate-issues

[Hibernate-JIRA] Created: (BVAL-214) Ability to validate an object and a list of changes

by Emmanuel Bernard (JIRA)

Ability to validate an object and a list of changes --------------------------------------------------- Key: BVAL-214 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-214 Project: Bean Validation Issue Type: Improvement Reporter: Emmanuel Bernard Pass a list of changes applied to an object graph and validate the object graph had the change been applied. This is useful for presentation layers like JSF for cross field validations for example. There are several possibilities to implement that: 1. pass in a Map<String,Object> with the list of changed properties {code}validator.validateObject(Object model,Map<String,Object> newValues, Class ...profile){code} 2. pass in a set of more typesafe changedset but essentially the same as 1. {code}changeSet.change("property", value).change("property2", null).remove("collection", index); validator.validateObject(Object model,ChangeSet changeSet, Class ...profile){code} 3. pass a proxy of the object and apply changes to the proxy. One of the benefits of this approach is that it is transparent to the validator API. The drawback is that the object must be proxyable {code}User proxiedUser = proxyfier.proxy(user); proxiedUser.setName("Emmanuel"); proxiedUser.getAddresses().add(address); validator.validateObject(Object proxiedUser, Class ...profile){code} More info from Alex {code} Client side validation already implemented in coming RichFaces 4.0 release, that's not a subject for bean validation. From the JSF side, the cool feature would be object validation that doesn't touch model itself. Currently, we can only validate a single bean attribute aganist new value, that doesn't allow. In richfaces, I do make a 'clone' of target object, update it with new values and perform validation on the cloned object. Would be nice to have something like: validator.validateObject(Object model,Map<String,Object> newValues, Class ...profile) that does a similar work.{code} -- 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, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5376) Tests contain invalid SQL

by Fred Toussi (JIRA)

Tests contain invalid SQL ------------------------- Key: HHH-5376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5376 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.x Environment: Using HSQLDB 2.0.1 and Hibernate trunk (12 July 2010) Reporter: Fred Toussi These create table statements declare both primary key and unique constraints on the same set of columns. This is against the SQL standard and will fail with most databases. public class DerivedIdentitySimpleParentSimpleDepTest extends TestCase { 22:52:06,265 ERROR SchemaExport:386 - Unsuccessful: create table MedicalHistory (lastupdate date, FK varchar(255) not null, primary key (FK), unique (FK)) 22:52:06,265 ERROR SchemaExport:387 - a UNIQUE constraint already exists on the set of columns in statement [create table MedicalHistory (lastupdate date, FK varchar(255) not null, primary key (FK), unique (FK))] public class DerivedIdentityIdClassParentSameIdTypeIdClassDepTest extends TestCase { public void testOneToOneExplicitJoinColumn() throws Exception { 23:16:18,328 DEBUG SchemaExport:415 - create table MedicalHistory ( FK1 varchar(255) not null, FK2 varchar(255) not null, primary key (FK1, FK2), unique (FK1, FK2) ) 23:16:18,328 ERROR SchemaExport:386 - Unsuccessful: create table MedicalHistory (FK1 varchar(255) not null, FK2 varchar(255) not null, primary key (FK1, FK2), unique (FK1, FK2)) 23:16:18,328 ERROR SchemaExport:387 - a UNIQUE constraint already exists on the set of columns in statement [create table MedicalHistory (FK1 varchar(255) not null, FK2 varchar(255) not null, primary key (FK1, FK2), unique (FK1, FK2))] -- 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, 4 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-6109) Implement new AnnotationBinder for new metamodel

by Hardy Ferentschik (JIRA)

Implement new AnnotationBinder for new metamodel ------------------------------------------------ Key: HHH-6109 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6109 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 4.0.0.Alpha2 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.Alpha3 New mapping binders need to be written for the new meta model. For the annotation side the plan is to * Replace commons-annotations w/ jandex (https://github.com/jbossas/jandex) * Handle most of the xml configuration by creating mock annotations in jandex * Use JAXB for XML parsing -- 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, 4 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-6287) Bind @Table.uniqueConstraint

by Strong Liu (JIRA)

Bind @Table.uniqueConstraint ---------------------------- Key: HHH-6287 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6287 Project: Hibernate Core Issue Type: Sub-task Reporter: Strong Liu Assignee: Strong Liu 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, 4 months

3
8
0 / 0

[Hibernate-JIRA] Created: (OGM-10) Discuss with Manik wether or not a copy on read is necessary

by Emmanuel Bernard (JIRA)

Discuss with Manik wether or not a copy on read is necessary ------------------------------------------------------------ Key: OGM-10 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-10 Project: Hibernate OGM Issue Type: Task Reporter: Emmanuel Bernard Fix For: 1.0-next >From what Manik said recently, they do marshal data when putting it in the map and thus a copy on read is not necessary. Clarify that and make sure mutable types do a proper copy on read if that's not the case. -- 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, 4 months

2
10
0 / 0

[Hibernate-JIRA] Created: (BVAL-241) Support Method Validation

by Gunnar Morling (JIRA)

Support Method Validation ------------------------- Key: BVAL-241 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-241 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Gunnar Morling Fix For: 1.1 As proposed in BV 1.0 Appendix C, the notion of method validation shall be established. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
8
0 / 0

[Hibernate-JIRA] Created: (OGM-18) Implement StatelessSession

by Emmanuel Bernard (JIRA)

Implement StatelessSession -------------------------- Key: OGM-18 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-18 Project: Hibernate OGM Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Priority: Minor low priority to me -- 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, 4 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5841) Invalid table creation in Annotations Test Cases

by Fred Toussi (JIRA)

Invalid table creation in Annotations Test Cases ------------------------------------------------ Key: HHH-5841 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5841 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.next Environment: Tested with HSQLDB 2.0.1 Reporter: Fred Toussi Some tests create a table with the definition like the one below. As Standard SQL does not allow two unique constraints (or one unique and one PK) on the same column(s) the table definition fails, resulting in test failure. 23:41:40,437 DEBUG SchemaExport:415 - create table MedicalHistory ( lastupdate date, FK varchar(255) not null, primary key (FK), unique (FK) ) The pattern of failure shows in several tests. For example: package org.hibernate.test.annotations.derivedidentities.e4.a; DerivedIdentitySimpleParentSimpleDepTest To reproduce, use an up-to-date HSQLDB 2.0.1 RC from http://hsqldb.org (I have not checked with 2.0.0, as this version has been superseded) -- 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, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4751) Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType

by David Coleman (JIRA)

Fix for @embeddedid error: Type not supported: org.hibernate.type.ManyToOneType -------------------------------------------------------------------------------- Key: HHH-4751 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4751 Project: Hibernate Core Issue Type: Improvement Components: envers Reporter: David Coleman Priority: Minor Attachments: IDMetadataGenerator_patch.txt Hi, After creating hibernate entities from the legacy database with envers hibernate tool, I noticed the following error occurred on creating an audit tables that has an @EmbeddedId attribute (related to ENVERS-76]: Caused by: org.hibernate.MappingException: Type not supported: org.hibernate.type.ManyToOneType .. I found out by looking at the source that the reason it failed was that the property type was not an instance of ImmutableType (not mutable); which was true as the embedded id was a combination of an int and a mutable java data object. I switched the mutable java date object to a immutable joda datetime object using the joda date time hibernate user type to fix the immutable problem. I also patched IdMetadataGenerator locally to the one attached as hibernate usertypes do not implement the ImmutableType interface; using the method 'isMutable()' should be suffice. Let me know if this is okay so I can submit the patch. -- 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, 4 months

7
29
0 / 0

[Hibernate-JIRA] Created: (HHH-5188) Use provided enum type ordinal/string when reading

by Stefan Larsson (JIRA)

Use provided enum type ordinal/string when reading -------------------------------------------------- Key: HHH-5188 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5188 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.0-CR-2 Reporter: Stefan Larsson Priority: Minor Attachments: EnumType.java-typeSafeNullSafeGet.patch When Hibernate reads a PostgreSQL enum type using ResultSet.getObject(), the JDBC driver returns a driver-specific PGObject object, which preserves both the value of the enum and its type ordinal/string. Hibernate fails with a ClassCastException when it attempts to cast the PGObject into a String in org.hibernate.type.EnumType.nullSafeGet(). The code in org.hibernate.type.EnumType assumes that ResultSet.getObject() will either return a Number or a String, which is not true for the PostgreSQL driver. IMHO it would be better to let the JDBC driver do the conversion using ResultSet.getInt() or getString() instead. The attached patch allows JBoss AS 6 M3 (Hibernate 3.5.0-CR-2) to read PostgreSQL enums, using JPA, with a a Java enum annotated as @javax.persistence.Enumerated(javax.persistence.EnumType.STRING). Also, I believe that perhaps ignoring the given enum type causes Issue HHH-4230, where an ordinal enum was stored in character field. ResultSet.getInteger() might work for that one depending on the JDBC driver. -- 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, 4 months

5
18
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2011