[
https://issues.apache.org/jira/browse/WW-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenzo Bernacchioni updated WW-3852:
-------------------------------------
Affects Version/s: (was: 2.2.1)
2.3.4
Fix Version/s: (was: 2.3.1)
2.3.4
Labels: i18n interceptors (was: )
Issue Type: Improvement (was: Bug)
with a customized textprovider the whole management of I18N messages can be
moved the a different resource (i.e DB instead properties), while text messages
for these interceptors remain 'stuck' on property-based resources.
> CLONE - FileUploadInterceptor and TokenInterceptor should use the configured
> custom TextProvider
> ------------------------------------------------------------------------------------------------
>
> Key: WW-3852
> URL: https://issues.apache.org/jira/browse/WW-3852
> Project: Struts 2
> Issue Type: Improvement
> Components: Core Interceptors
> Affects Versions: 2.3.4
> Reporter: Lorenzo Bernacchioni
> Assignee: Maurizio Cucchiara
> Labels: i18n, interceptors
> Fix For: 2.3.4
>
>
> 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
