You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Herbert (JIRA)" <ji...@apache.org> on 2011/01/04 22:46:45 UTC
[jira] Updated: (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:all-tabpanel ]
Herbert updated WW-3552:
------------------------
Description:
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?
was:
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 doesn't use this new custom TextProvider hence it uses XWork's LocalizedTextUtil class to lookup translations. Why the translations don't get resolved via an injected TextProvider?
Summary: FileUploadInterceptor and TokenInterceptor should use the configured custom TextProvider (was: File Upload Interceptor Support for custom TextProviders)
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.