If I understand you correctly Thiago, this will require me to 'wrap' all the servlets individually, i.e. the tapestry part would have to know about all the servlets, which isn't desirable. Or am I missing something?
On Sep 8, 2011, at 12:43 PM, Lenny Primak wrote: > no but I will try :) > > On Sep 8, 2011, at 12:41 PM, Thiago H. de Paula Figueiredo wrote: > >> On Thu, 08 Sep 2011 13:39:41 -0300, Lenny Primak <lpri...@hope.nyc.ny.us> >> wrote: >> >>> I have a servlet which I need to use as part of the Tapestry web app. >>> Since it's not an asset, etc. Tapestry completely ignores it. >>> Is there any way to add it to the pipeline? >> >> Have you tried wrapping it in a HttpServletRequestFilter and adding it to >> the HttpServletRequestHandler service? >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and >> instructor >> Owner, Ars Machina Tecnologia da Informação Ltda. >> http://www.arsmachina.com.br >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
