You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2009/09/08 17:31:57 UTC
[jira] Resolved: (WINK-155) Deploy Wink as a servlet filter
[ https://issues.apache.org/jira/browse/WINK-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryant Luk resolved WINK-155.
-----------------------------
Resolution: Fixed
I added the filter implementation. One difference from the RestServlet is that the filter does not take into account the URL mapping directly. (i.e. whereas the servlet uses context-root/servlet-path/root resource path, the filter uses context-root/root resource path). Also if the filter is set to only use url-mapping of /foo/*, a byproduct is that only root resources with /foo/* would be invoked.
> Deploy Wink as a servlet filter
> -------------------------------
>
> Key: WINK-155
> URL: https://issues.apache.org/jira/browse/WINK-155
> Project: Wink
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.1
> Reporter: Michael Elman
> Assignee: Bryant Luk
> Fix For: 0.2
>
>
> Following the discussion in the mailing list (http://n2.nabble.com/Use-case-deploy-wink-as-a-servlet-filter-td3515605.html#a3515605)
> We should be able to deploy Wink as servlet filter. For the 404 responses, the request should propagate to the servlets layer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.