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 us
I am running Tap5 from Jetty using the Maven2 jetty:run plugin.
All works fine with the following in the web.xml:
TapestryFilter
/*
When I change to this:
TapestryFilter
/app/*
and browse to /app/ under the web context, I get a 404. There are no errors
in the logs.
Can a