[ 
https://issues.apache.org/jira/browse/DELTASPIKE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek resolved DELTASPIKE-889.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.1
         Assignee: Thomas Andraschko

just fyi:
if you don't need this feature and it just blocks you, you can deactivate it 
via JsfModuleConfig#isContainerManagedValidatorsEnabled and 
JsfModuleConfig#isContainerManagedConvertersEnabled

i couldn't reproduce the issue, because i saw a different one.
however, since we re-implemented that part it's different with the next release 
anyway and here the new implementation works also with wildfly. 

-> please re-test it with the latest snapshot to avoid that you still see the 
issue with the upcoming release.

> ValidatorWrapper causes filtering of multiple custom validators in 
> ValidatorTagHandler
> --------------------------------------------------------------------------------------
>
>                 Key: DELTASPIKE-889
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-889
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: JSF-Module
>    Affects Versions: 1.3.0
>         Environment: JSF 2.2 / Wildfly 8.1 
>            Reporter: Thomas Frühbeck
>            Assignee: Thomas Andraschko
>             Fix For: 1.3.1
>
>
> InjectionAwareApplicationWrapper wraps custom validators.
> In ValidatorTagHandlerDelegateImpl the check for class equality causes a 
> unique constraint on validators, so effectively filtering all "wrapped" 
> validators but the first:
>         for (Validator validator : validators) {
>             if (validator.getClass().equals(v.getClass())) {
>                 found = true;
>                 break;
>             }
>         }
>         
>         if (!found) {
>             evh.addValidator(v);
>         }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to