On Thu, Mar 12, 2009 at 4:16 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
> 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. But if the page is an index page, then the page matches 'any name'. It'd be nice to be able to have a page that could match a subset -- in some cases, just to get something like a "/" url instead of a "/start" url. In other cases, because you want to match, say, data-driven values. (e.g. I want to be able to respond to /client/ibm and /client/apple, but since Dell isn't a client, I don't want to respond to /client/dell) I agree that I /could/ handle this by, for instance, bringing up the client page and saying "Dell isn't a client". In many cases, that's probably the sensible approach. But that won't always be the best match. In this case, I want to have an Index so that page links to the root go to "/", but I also want to be able to reject requests for "/foo" with a simple 404. What I want may not be something that Tapestry really intends to cover. :) Such is life. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
