[jira] [Commented] (WW-4160) Construct UnknownHandler using Spring

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on WW-4160:
-----------------------------------------------------

Commit de5edd875fa766ad6214b7b4aef8daf369d360ea in struts's branch refs/heads/develop from [~lukaszlenart]
[ https://git-wip-us.apache.org/repos/asf?p=struts.git;h=de5edd8 ]

WW-4160 Adds UnknownHandlerFactory to allow override
This can be used to implement different factories with different
backing DI container ie. Spring


> Construct UnknownHandler using Spring
> -------------------------------------
>
>                 Key: WW-4160
>                 URL: https://issues.apache.org/jira/browse/WW-4160
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Plugin - Spring, XML Configuration
>    Affects Versions: 2.3.15.1
>            Reporter: Jasper Rosenberg
>            Priority: Minor
>             Fix For: 2.3.18
>
>
> I have a custom unknown handler in my struts2 definition (to return a 404 in production if the method is not found).  I would like to have the handler constructed by Spring instead of the xwork container though so that I can have some other logging/debugging resources injected.
> {code}
>     <bean type="com.opensymphony.xwork2.UnknownHandler" name="pageNotFoundUnknownHandler" class="com.mycompany.PageNotFoundUnknownHandler"/>
>     <unknown-handler-stack>
>        <unknown-handler-ref name="pageNotFoundUnknownHandler" />
>     </unknown-handler-stack>
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)