[
https://issues.apache.org/jira/browse/WINK-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921498#action_12921498
]
Hudson commented on WINK-319:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #394 (See
[https://hudson.apache.org/hudson/job/Wink-Trunk-JDK1.5/394/])
Fix issue with user handler method signature
Thanks to Luciano Resende for pointing out the issue.
See [WINK-319]
Simplify addition of Request/Response handlers
Thanks to Luciano Resende for the patch.
See [WINK-319]
> Simplify addition of Request/Response handlers
> ----------------------------------------------
>
> Key: WINK-319
> URL: https://issues.apache.org/jira/browse/WINK-319
> Project: Wink
> Issue Type: Improvement
> Components: Server
> Affects Versions: 1.1.1
> Reporter: Luciano Resende
> Assignee: Bryant Luk
> Fix For: 1.1.2
>
> Attachments: WINK-319.patch
>
>
> Currently, embedding Wink requires extending multiple Wink Server classes,
> particularly if you want to add special handlers etc. It seems that some of
> this could be simplified, particularly in the case of adding user specific
> handlers. I was wondering if, instead of having to provide my own
> DeploymentConfiguration that needs to
> override the specific handler initialization method, we could expose the
> actual list of handlers in the Wink DeploymentConfiguration and allow
> embedders to add new handlers to this list in the getDeploymentConfiguration
> in the Servlet ? This might also require some updates on how the handler
> chain is processed, basically delaying the initialization of the handler
> chain or updating the AbstractHandlersChain to process userHandlers and
> Handlers as two separate lists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
