[jira] [Commented] (WW-3905) The TextProvider injection in ActionSupport isn't quite integrated into the framework's core DI

["Lukasz Lenart (JIRA)" <ji...@apache.org>]

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

Lukasz Lenart commented on WW-3905:
-----------------------------------

I found out a solution - use TextProviderFactory instead directly call to create TextProvider. I'm going extract TextProviderFactory to be an interface with default implementation and then will change all the code to use TextProviderFactory instead of TextProvider.
                
> The TextProvider injection in ActionSupport isn't quite integrated into the framework's core DI 
> ------------------------------------------------------------------------------------------------
>
>                 Key: WW-3905
>                 URL: https://issues.apache.org/jira/browse/WW-3905
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Actions
>    Affects Versions: 2.3.4.1
>            Reporter: chad davis
>              Labels: ActionSupport, DependencyInjection, TextProvider
>             Fix For: 2.3.9
>
>
> The injection of the TextProvider into ActionSupport occurs via a lazy initialization in the getTextProvider() method.  This method obtains the TextProvider from a factory that has the implementation injected into it via  the core di mechanism.  The problem with this is that ActionSupport programmatically does the injection using it's reference to the core ContainerImpl.  This makes it impossible to use the Spring plugin's SpringObjectFactory to manage this TextProvider.    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira