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
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
Use of example in ConstraintFactory section (2.4)
-------------------------------------------------
Key: BVAL-7
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-7
Project: Bean Validation
Issue Type: Task
Components: spec-general
Reporter: Hardy Ferentschik
Priority: Minor
Just wondering what the example 2.4.1 shall demonstrate in section 2.4? Is just shows a validator implementation, but the section is about the ConstraintFactory. I think this example can be removed,
--
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
Change order of exmaple classes in Book/Author example
------------------------------------------------------
Key: BVAL-5
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-5
Project: Bean Validation
Issue Type: Task
Components: spec-general
Reporter: Hardy Ferentschik
Priority: Minor
I think the example in Section 3.6 "Examples" with the classes Author and Book is easier to understand if the Book class is listed before the Author class.
--
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
Replace array return types with Sets
------------------------------------
Key: BVAL-3
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-3
Project: Bean Validation
Issue Type: Task
Components: spec-general
Reporter: Hardy Ferentschik
the following methods in the Spec return arrays. They should return sets of the appropriate types:
InvalidConstraint.getGroups()
ConstraintDescriptor.getGroups()
ElementDescriptor.getConstraintDescriptors()
--
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