|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
This might actually take quite some time. In PropertyMetaData we'll have to keep all the constraints, but in different buckets, so that all constraints are evaluated when validating the complete bean, but only the sub-type meta data when calling validator.validateProperty(sub, "i").
Maybe MetaDataBuilder#accepts() should return three possible values: ACCEPTS, HIDES, DOESNT_ACCEPT, signaling that the supertype metadata needs to be added to another builder, using another name than the simple property one in order to keep constraints on the hiding and the hidden member separate.