November 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-261) Let composed constraint return the message of the first failing constraint instead of the composed constraint

by Emmanuel Bernard (JIRA)

Let composed constraint return the message of the first failing constraint instead of the composed constraint ------------------------------------------------------------------------------------------------------------- Key: BVAL-261 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-261 Project: Bean Validation Issue Type: Improvement Reporter: Emmanuel Bernard A better name is needed but to get the idea @ReportAsSingleViolation(messageSource=ByOriginatingConstraint) This would return the composing constraint message (say from @Size) instead of the composed constraint @ZipCode -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-555) Improve toString() in ConstraintViolationException

by David J. M. Karlsen (JIRA)

Improve toString() in ConstraintViolationException -------------------------------------------------- Key: HV-555 URL: https://hibernate.onjira.com/browse/HV-555 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.2.0.Final Environment: N/A Reporter: David J. M. Karlsen It would be nice if the mesage from ConstraintViolationException was better so that when logging it would show the beanpath and errors by default. Today it will just read: {noformat} javax.validation.ConstraintViolationException: null {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
5
0 / 0

[Hibernate-JIRA] Created: (BVAL-267) Provide a ConstraintViolationException builder to facilitate consumer code

by Emmanuel Bernard (JIRA)

Provide a ConstraintViolationException builder to facilitate consumer code -------------------------------------------------------------------------- Key: BVAL-267 URL: https://hibernate.onjira.com/browse/BVAL-267 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-285) ValidatorFactory#close should clearly state post condidtions

by Hardy Ferentschik (JIRA)

ValidatorFactory#close should clearly state post condidtions ------------------------------------------------------------- Key: BVAL-285 URL: https://hibernate.onjira.com/browse/BVAL-285 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.1.next Reporter: Hardy Ferentschik The Javadocs for ValidatorFactory#close says: {quote} After the _ValidatorFactory_ instance is closed, it is not allowed to call: * methods of this _ValidatorFactory_ instance * methods of _Validator_ instances created by this _ValidatorFactory_ {quote} It does, however, not specified what happens if such a method is called. I think with this wording a post conditions needs to be specified, eg a _ValidationException_ will be thrown. Otherwise the docs should say that the behavior is unspecified if any of the mentioned methods is called after calling _close()_ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
8
0 / 0

[Hibernate-JIRA] (BVAL-319) Move description of JSF integration from JSF spec to BV spec

by Hardy Ferentschik (JIRA)

11 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] (BVAL-302) Return constraint violations as a graph

by George Sapountzis (JIRA)

11 years, 11 months

4
4
0 / 0

[Hibernate-JIRA] (BVAL-325) Clarify how Java EE CDI and the BV provider portable extensions interact for the default components

by Emmanuel Bernard (JIRA)

11 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] (BVAL-324) Find a solution to register only a single interceptor for method-validation

by Emmanuel Bernard (JIRA)

11 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-7000) Avoid initializing proxy when using covariant return types for ID getters

by Michael Rudolf (JIRA)

Avoid initializing proxy when using covariant return types for ID getters ------------------------------------------------------------------------- Key: HHH-7000 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-7000 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Michael Rudolf When using an entity hierarchy with overridden ID getters and covariant return types, Hibernate does not detect ID getter calls and unnecessarily initializes proxies in order to call the methods instead of just returing the ID. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3502) getIdentifierMethod of BasicLazyInitializer does not match if method invoked through an interface with different return type

by Sean Bridges (JIRA)

getIdentifierMethod of BasicLazyInitializer does not match if method invoked through an interface with different return type ---------------------------------------------------------------------------------------------------------------------------- Key: HHH-3502 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3502 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Reporter: Sean Bridges Priority: Minor I have an entity interface, public interface IEntity { public Object getId(); } and I have an entity, say User that implements this interface with an id method @Id public Long getId() { return id; } I can call getId() on an uninitialized proxy with, user.getId() however, if I call getId() in this way, ((IEntity) user)).getId() I get org.hibernate.LazyInitializationException: could not initialize proxy - no Session Looking at the code, BasicLazyInitializer has these lines, else if ( isUninitialized() && method.equals(getIdentifierMethod) ) { return getIdentifier(); } the method.equals(getIdentifierMethod) returns false. The methods are not equal() because they have different return types (this is allowed in 1.5 with covariant return types). Hibernate should not use Method.equals(), but should instead use the code below (modified from Method.equals(Object)), public boolean equalsIgnoringReturnType(Method m1, Method m2) { if ((m1.getDeclaringClass() != m2.getDeclaringClass()) { return false; } if (m1.getName() != m2.getName()) { return false; } Class[] params1 = m1.getParameterTypes(); Class[] params2 = m2.getParameterTypes(); if (params1.length != params2.length) { return false; } for (int i = 0; i < params1.length; i++) { if (params1[i] != params2[i]) return false; } return true; } -- 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

11 years, 11 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2012