August 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (OGM-67) Infinispan configuration requires writeSkewCheck=true

by Sanne Grinovero (JIRA)

Infinispan configuration requires writeSkewCheck=true ----------------------------------------------------- Key: OGM-67 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-67 Project: Hibernate OGM Issue Type: Bug Components: core, documentation Reporter: Sanne Grinovero Assignee: Sanne Grinovero The MVCC capabilities of Infinispan need to be explicitly enabled using the writeSkewCheck flag -- 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
3
0 / 0

[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, 4 months

3
3
0 / 0

[Hibernate-JIRA] (HBX-1208) Tests in Error When Using JDK 1.7

by Koen Aers (JIRA)

12 years, 4 months

1
2
0 / 0

[Hibernate-JIRA] (HBX-1211) Placeholder for fix for branch master

by Koen Aers (JIRA)

12 years, 4 months

1
3
0 / 0

[Hibernate-JIRA] (HBX-1210) Placeholder for fix for branch 3.6.x

by Koen Aers (JIRA)

12 years, 4 months

1
3
0 / 0

[Hibernate-JIRA] (HBX-1209) Placeholder for fix for branch 3.4.x

by Koen Aers (JIRA)

12 years, 4 months

1
3
0 / 0

[Hibernate-JIRA] (HHH-7469) Implement @OneToMany support

by Hardy Ferentschik (JIRA)

12 years, 4 months

2
2
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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2012