struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diego Díez (JIRA) <j...@apache.org>
Subject [jira] Commented: (WW-3552) FileUploadInterceptor and TokenInterceptor should use the configured custom TextProvider
Date Sat, 12 Feb 2011 00:35:59 GMT

    [ https://issues.apache.org/jira/browse/WW-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993774#comment-12993774
] 

Diego Díez commented on WW-3552:
--------------------------------

I've solved my problem adding this piece of code instead using LocalizedTextUtil class:

if (action instanceof TextProvider) {
   message = ((TextProvider)action).getText(messageKey);
}

It do the trick for me

> 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
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message