During schema generation using AnnotationConfiguration, the ClassValidator is skipping members of embedded components with custom @ValidatorClass annotations.

There is a fairly easy change to ClassValidator.createMemberValidator() to check if the memberAnnotation is a Embedded, then recursively add the embedded members to the memberValidators and memberGetters collections (of ClassValidator).

Unfortunately, the BinderHelper.findPropertyByName method (3.2.1.ga) and the ClassValidator.findPropertyByName method (latest version) don't recursively find the actual property/member, and thus ClassValidator.apply() skips applying the property validation on embedded attributes.

Any suggestions regarding a workaround for 3.2.1.GA of annotations, or the prospect this will be fixed in a future release.

Hi,
did you try using ?
This should instruct the framework to recursively test validation on referenced objects,
I didn't try it on embedded components but it should work.

regards,

Sanne - Thanks for the reply.

@Valid did not work for embedded attributes. However, if I put my custom validation check annotation on the embedded attribute itself, my validator class is called. Via iterating columns on the property's value attribute, I was able to add the check constraint to each of the embedded class' attributes.

Unfortunately, within the PropertyConstraint.apply() method, I only have access to the property and its 'value", and can't seem to get access to any of the member annotations. Thus, this approach only works if all enbedded component members need this check constraint.

This appears to be related to the topic

[url]http://forum.hibernate.org/viewtopic.php?t=975612&highlight=
[/url]

There is a bug report covering this (HV-25). Voting for the bug may increase the likelihood of it being fixed.