hi markus, jsf 2.2 introduced some incompatibilities impacting the (out-of-the-box) forward compatibility of extval (as it was available for jsf 2.1). if you are interested in it, please file a feature-request/jira-ticket.
regards, gerhard 2016-09-28 6:56 GMT+02:00 md <[email protected]>: > Hi all, > we use ExtVal especially for CrossValidation. We migrate an application > from > jsf 1.2 to 2.2 and we want to use BeanValidation. > In cases of validation during ajax request, for every request another > BeanValidator is added to the component. This leads to redundant > validationerrors. > > This is because of ExtValAplicationWrapper's implementation of > addDefaultValidatorId method, which prevents "javax.faces.Bean" added as > defaultValidatorId. > > Is this expected behavior or should I file a bug? > > Thanks in advance. > > Markus > > > > -- > View this message in context: http://myfaces.10567.n7.nabble > .com/EXTVAL-DefaultValidatorId-will-not-be-set-tp122266.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. >
