Tapestry is distinguishing two cases: For page render requests, URL paths that look like actual pages, but do no match an actual page, are handed off to the servlet container. You'll see standard 404 behavior.
For component event requests, if the page name is not an actual page you again get 404 behavior. Only if the page name is a known page name but there are other errors (references to components that do not exist) is this treated as a Tapestry error. On Thu, Mar 12, 2009 at 12:41 PM, Geoffrey Wiseman <geoffrey.wise...@gmail.com> wrote: > On Thu, Mar 12, 2009 at 3:15 AM, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > >> - If you distinguish between requests that are handled within the >> application context, and outside of the context, i.e.: by the container, >> then you can devise a more effective solution to handle these errors... > > > Probably - although in this case the way 'index' pages work is creating that > issue for me. I could always live with the /start URL I suppose. ;) > > I don't know much about RequestFilter / Dispatcher in T5 yet; I'll look into > those. > > - Geoffrey > -- > Geoffrey Wiseman > http://www.geoffreywiseman.ca/ > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
