struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukasz Lenart (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (WW-3552) FileUploadInterceptor and TokenInterceptor should use the configured custom TextProvider
Date Sat, 21 Jul 2012 11:17:35 GMT

     [ https://issues.apache.org/jira/browse/WW-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lukasz Lenart resolved WW-3552.
-------------------------------

    Resolution: Fixed

Done, added support for custom TextProvider and change getTextMessage() methods to be protected
                
> 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: Lukasz Lenart
>             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

        

Mime
View raw message