[
http://jira.jboss.com/jira/browse/JBSEAM-2245?page=comments#action_12387519 ]
dapeng wang commented on JBSEAM-2245:
-------------------------------------
I know there is this workaround. I am filing a bug report for validateAll component and
you tell me to use other components. But the bug won't get fixed in this way. If you
provide validateAll, which is really reasonable in my eyes, then make sure it works.
I just don't understand why you won't fix it, because it costs no more than 2
minutes. Other users as jbuechel also spent hours on this bug. (See forum),
Custom validator disables hibernate default validator
-----------------------------------------------------
Key: JBSEAM-2245
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2245
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 2.0.0.GA
Reporter: dapeng wang
Assigned To: Pete Muir
Fix For: 2.0.1.GA
The default hibernate validator doesn't work anymore, as soon as a custom validator
is added to the component, though the text field is put inside a validateAll tag.
In the class ValidateAllRendererBase following code is found, which is buggy in my
opinion:
if ( evh.getValidators().length==0 && evh.getValidators().length == 0 )
{
evh.addValidator( new ModelValidator() );
}
First of all, I don't understand, why you check the same condition twice. Second, I
have no clue, why you only add the ModelValidator, if here is no other validator. I would
exactly like to combine the hibernate validator with my custom one.
Pleas remove the if check. I would also like to help and fix this bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira