You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/06/27 13:42:24 UTC

[jira] [Commented] (WW-4346) Nested visitor validator returns wrong full field name

    [ https://issues.apache.org/jira/browse/WW-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045844#comment-14045844 ] 

ASF subversion and git services commented on WW-4346:
-----------------------------------------------------

Commit 3a07c317724c1f8017be93f0e1bae23392c08fc6 in struts's branch refs/heads/develop from [~lukaszlenart]
[ https://git-wip-us.apache.org/repos/asf?p=struts.git;h=3a07c31 ]

WW-4346 Solves problem with nested visitor validator returns wrong full field name

Closes #13


> Nested visitor validator returns wrong full field name
> ------------------------------------------------------
>
>                 Key: WW-4346
>                 URL: https://issues.apache.org/jira/browse/WW-4346
>             Project: Struts 2
>          Issue Type: Bug
>            Reporter: Aleksandr Mashchenko
>              Labels: patch
>             Fix For: 2.3.18
>
>         Attachments: tests-visitor-full-field-name.diff, visitor-full-field-name.diff
>
>
> Original issue report: http://stackoverflow.com/questions/23544452/chaining-visitor-validator-in-struts-2.
> This bug can be reproduced by nesting two or more visitor validators with a conversion validator in the last validation configuration.
> Conversion validator in nested visitor validators doesn't work as expected because getFullFieldName method in VisitorFieldValidator.AppendingValidatorContext returns not a full field name.
> This patch makes sure that the correct full field name is returned.
> Also the InternalValidatorContextWrapper-s from AnnotationActionValidatorManager and DefaultActionValidatorManager could be removed because they were introduced to fix similar issue with nested visitor validators. See https://issues.apache.org/jira/browse/XW-588 and https://issues.apache.org/jira/browse/XW-618 for more details.



--
This message was sent by Atlassian JIRA
(v6.2#6252)