[
https://issues.apache.org/jira/browse/DELTASPIKE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525478#comment-14525478
]
Gerhard Petracek commented on DELTASPIKE-889:
---------------------------------------------
no and with the current snapshot you can e.g. also drop javassist.
if you like to debug it - it's in InjectionAwareApplicationWrapper
#managedOrDefaultConverter and #managedOrDefaultValidator.
with the current snapshot you shouldn't see ConverterWrapper or
ValidatorWrapper for custom tags, because #resolveManagedConverter and
#resolveManagedValidator should find the result/s which will get returned (if
the converters and validators are valid - see
ConverterAndValidatorProxyExtension)
> 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.4.0
>
>
> 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)
