Hmm... It looks like leaving the default mapping in place allows the
tapestry filter to run (and I assume take care of my perthread cleanup) and
does not interfere with my other servlet mappings. Very nice.
Ben
On 6/7/07, Ben Tomasini <[EMAIL PROTECTED]> wrote:
I am running Tap5 from Jetty using the Maven2 jetty:run plugin.
All works fine with the following in the web.xml:
<filter-mapping>
<filter-name>TapestryFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
When I change to this:
<filter-mapping>
<filter-name>TapestryFilter</filter-name>
<url-pattern>/app/*</url-pattern>
</filter-mapping>
and browse to /app/ under the web context, I get a 404. There are no
errors in the logs.
Can anyone else reproduce this?
I have a need to put tapestry under this path to make room for some
servlets with wildcard mappings under other paths.
Ben
