Issue Type: Improvement Improvement
Affects Versions: 1.1.0.Beta3
Assignee: Unassigned
Components: spec-general
Created: 14/Feb/13 5:36 PM
Description:

A note in 5.1.1 mentions that the case of field/property hiding in hierarchies is unspecified and will be clarified in a later revision.

I guess it's too late to address this for 1.1, but if we ever will, the following rules might make sense:

  • In case a complete bean is validated, constraints on hidden and hiding members are evaluated (the members can be independently discovered and metadata such as constraints gathered for these)
  • In case a single property is validated (validateProperty, validateValue), only the hiding member gets validated (validateValue could be invoked for the supertype member separately, for validateProperty I don't see a way how the hidden member could be targeted)
  • The metadata API exposes the hiding member only (metadata for the hidden member could be retrieved from the supertype)
Fix Versions: 1.1.0.maybe
Project: Bean Validation
Priority: Major Major
Reporter: Gunnar Morling
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira