Define validation Context to be passed to constraint implementation calls
-------------------------------------------------------------------------
Key: BVAL-30
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-30
Project: Bean Validation
Issue Type: New Feature
Components: spec-general
Reporter: Emmanuel Bernard
Need a way to forbid called to addErrorMessage(String, String property) if the bean instance is not defined.
--
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
Should ConstraintDescriptor.getConstraintImplementation() replaced by .getConstraintImplementationClass()?
----------------------------------------------------------------------------------------------------------
Key: BVAL-33
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-33
Project: Bean Validation
Issue Type: Improvement
Components: spec-general
Reporter: Emmanuel Bernard
I don't see a use case for exposing the actual implementation instance, especially since Context has been added to the Constraint signature.
ConstraintDescriptor could then be used as a metadata container between a Constraint resolution strategy and the BV core engine wo having to pass the constraintFactory as a dependency. It would also make CD serializable.
--
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
StandardConstraint description (2.5)
------------------------------------
Key: BVAL-8
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-8
Project: Bean Validation
Issue Type: Task
Components: spec-general
Reporter: Hardy Ferentschik
Priority: Minor
Last sentence:
"Clients can then access this information through the Constraint metadata request API and more specifically through the getConstraintImplementation method of ConstraintDescriptor."
The call to getConstraintImplementation() will only give you access to the actual Constraint. You still have to call getStandardConstraints() (provided that the constraint implements StandardConstraint)
--
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