This is interesting because I will probably be doing the same thing soon to integrate the DWR servlet with tapestry. I guess you will need to instantiate the servlet and set the "init-params" on it. I was thinking of configuring the values as http://tapestry.apache.org/symbols.html tapestry symbols and passing them as init-params to the servlet.
NB. To deal with a servlet you will be needing HTTPServletRequest and HTTPServletResponse so it is better to implement a org.apache.tapestry5.services.HttpServletRequestFilter and contribute it to the HttpServletRequestHandler instead of contributing a RequestFilter to the RequestHandler as I suggested before (on works with the raw servlet objects and the other works with tapestry's wrapper objects). I'm guessing that you will map the servlet to a path (eg "/vaadin/.*") and will only pass to the servlet for paths that match (and return true) or return false otherwise to allow tapestry to process the request. I'm interested to hear how you get along as I will be doing the http://tapestry.1045711.n5.nabble.com/tapestry-push-proof-of-concept-td5697644.html same thing soon . Cheers, Lance. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Getting-Session-State-Object-from-another-servlet-alongside-Tapestry-tp5696382p5702313.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
