Guys, I've been trying to search google and nabble for this, but just couldn't find the answer, perhaps I'm just using the wrong keywords or something... as I'm sure it will sound trivial to some of you.
Here's what I'm trying to achieve: I'd like to implement a simplistic API in our webapplication using just a plain old servlet to handle all API method calls. The idea is to just call this single servlet, passing in the required set of parameters via GET/POST, and responding with a either an XML data response (text/xml), or a binary stream (zipped data) depending on the method called. Now, I'm lost trying to find the best way how to mix this into the existing Tapestry5 application. I have tried to just add the servlet/mapping into web.xml but that doesn't work. I thought about extending TapestryFilter to ignore the API servlet's path, but the doFilter method is "final" right? I also thought about just getting the raw http request/response within a tapestry page using injection, but that just doesn't feel right - it seems better to bypass tapestry altogether for this purpose, or is it wrong? Thanks for any ideas in advance! Rado -- View this message in context: http://www.nabble.com/T5%3A-How-to-implement-a-simple-API-servlet--tp19149751p19149751.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
