You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Aleksandr Mashchenko (JIRA)" <ji...@apache.org> on 2014/05/14 21:17:14 UTC
[jira] [Updated] (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:all-tabpanel ]
Aleksandr Mashchenko updated WW-4346:
-------------------------------------
Attachment: visitor-full-field-name.diff
> 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
> Attachments: 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)