You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lorenzo Bernacchioni (JIRA)" <ji...@apache.org> on 2012/07/17 15:58:35 UTC
[jira] [Commented] (WW-3552) FileUploadInterceptor and
TokenInterceptor should use the configured custom TextProvider
[ https://issues.apache.org/jira/browse/WW-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416200#comment-13416200 ]
Lorenzo Bernacchioni commented on WW-3552:
------------------------------------------
I agree, FileUploadInterceptor should get messages in the same way actions (and validations and other stuff) do.
Moreover the signature of the method
private String getTextMessage(Object action, String messageKey, Object[] args, Locale locale)
cannot be overridden by customized implementation.
Could at least be a protected method?
Meanwhile I have to override the whole interceptor just to put the line suggested by Diego Díez.
> FileUploadInterceptor and TokenInterceptor should use the configured custom TextProvider
> ----------------------------------------------------------------------------------------
>
> Key: WW-3552
> URL: https://issues.apache.org/jira/browse/WW-3552
> Project: Struts 2
> Issue Type: Bug
> Components: Core Interceptors
> Affects Versions: 2.2.1
> Reporter: Herbert
> Assignee: Maurizio Cucchiara
> Fix For: 2.3.1
>
>
> Struts2 supports the usage of a custom text provider by setting some environment constants in struts.xml:
> example:
> <bean class="test.CustomTextProvider" name="myTextProvider" type="com.opensymphony.xwork2.TextProvider" />
> <constant name="struts.xworkTextProvider" value="myTextProvider" />
> The struts2 core FileUploadInterceptor and the TokenInterceptor don't use this new custom TextProvider hence they use XWork's LocalizedTextUtil class to lookup translations. Why the translations don't get resolved via an injected TextProvider?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira