On Wed, 26 Feb 2014 06:57:27 -0300, garz wrote:
Hi,
Hi!
i was just curious about why Tapestry is using a Filter instead of a
Servlet. Does anyone know?
As Lance said, a servlet is and endpoint and it must send a response to a
request. This causes servlets to be useless when you're tryi
thank you, thats it :)
On 26.02.2014, at 11:22, Lance Java wrote:
> Well... You can have the Tapestry filter mapped to /* and it can play
> nicely with other servlets.
>
> http://tapestry.apache.org/configuration#Configuration-ConfiguringIgnoredPaths
---
Well... You can have the Tapestry filter mapped to /* and it can play
nicely with other servlets.
http://tapestry.apache.org/configuration#Configuration-ConfiguringIgnoredPaths
yes i know that, but it does not answer my question. :)
On 26.02.2014, at 11:09, Lance Java wrote:
> A filter is passed a reference to the FilterChain which can ultimately pass
> through to the servlet container's own url resolution (ie a resource in the
> war).
>
> A servlet is an endpoint and
A filter is passed a reference to the FilterChain which can ultimately pass
through to the servlet container's own url resolution (ie a resource in the
war).
A servlet is an endpoint and must resolve the URL itself.
