[
https://issues.apache.org/jira/browse/WW-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950542#comment-13950542
]
Hudson commented on WW-4202:
----------------------------
SUCCESS: Integrated in Struts-JDK6-develop #32 (See
[https://builds.apache.org/job/Struts-JDK6-develop/32/])
WW-4202 Solves problem with using wrong TextProvider for ModelDriven
(lukaszlenart: rev a6017dcac42123cc41144d0d607210aa7d7c8907)
*
xwork-core/src/test/java/com/opensymphony/xwork2/validator/VisitorFieldValidatorTest.java
*
xwork-core/src/main/java/com/opensymphony/xwork2/validator/DelegatingValidatorContext.java
*
xwork-core/src/test/resources/com/opensymphony/xwork2/TestBean-beanMessageBundle-validation.xml
> CustomTextProvider not used for validation errors of model driven actions
> -------------------------------------------------------------------------
>
> Key: WW-4202
> URL: https://issues.apache.org/jira/browse/WW-4202
> Project: Struts 2
> Issue Type: Bug
> Components: Annotations, XML Validators
> Affects Versions: 2.3.15.1
> Reporter: Christoph Nenning
> Assignee: Lukasz Lenart
> Priority: Minor
> Fix For: 2.3.17
>
>
> When an application registers it's own TextProvider via
> 'struts.xworkTextProvider' in struts.xml, it is not used for validation
> errors of Model-Members of ModelDriven actions.
> Łukasz commented on the mailing list:
> > There is a bug in DelegatingValidatorContext#makeTextProvider method -
> > it should first try to use parent before creating new instance of
> > TextProvider (base on TextProviderFactory but without injecting
> > dependencies :\)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
