Resteasy filter should be implemented as a RequestFilter rather than a HttpServletRequestFilter

Alejandro Scandroli added a comment - 23/May/12 4:51 PM I remember this was a deliberate decision but I can't remember the reasoning behind it I'll try to remember or at least I'll make it configurable.

Alejandro Scandroli added a comment - 16/Nov/12 5:52 PM We don't want resteasy to be mixed with all the Tapestry's built-in filters. We wan resteasy to be executed in the HttpServletRequestHandler pipeline. If you can't live without the Request and the Response from the RequestHandler pipeline you can monkey patch them in with something like this: /** * This is needed because the PageRenderLinkSource uses the Request to create URLs and we need to be able to create * URLs from REST services. */ @Contribute(HttpServletRequestHandler.class) public void storeRequestIntoGlobalsMonkeyPath(OrderedConfiguration<HttpServletRequestFilter> configuration, @Symbol(SymbolConstants.CHARSET) final String applicationCharset, final TapestrySessionFactory sessionFactory, final RequestGlobals requestGlobals) { HttpServletRequestFilter storeIntoGlobals = new HttpServletRequestFilter() { public boolean service(HttpServletRequest servletRequest, HttpServletResponse servletResponse, HttpServletRequestHandler handler) throws IOException { Request request = new RequestImpl(servletRequest, applicationCharset, sessionFactory); Response response = new ResponseImpl(servletRequest, servletResponse); requestGlobals.storeRequestResponse(request, response); return handler.service(servletRequest, servletResponse); } }; configuration.add( "StoreRequestIntoGlobals" , storeIntoGlobals, "before:SecurityConfiguration" ); }