On Mon, Jun 7, 2010 at 10:31 AM, Todd Orr <torr0...@gmail.com> wrote: > This works. However, it is awkward as now I need to specifically refer to my > start page rather than the directory, somedir/start vs somedir/. I hope this > is resolved in future releases.
What I do is that I use a Start page at the root level (which is rendered if user requests just the root context) and Index pages in sub-directories - if users get at least the directory right in the latter case I can then handle showing 404s manually in onActivate() if I need to). But yes, the built-in logic is perhaps a bit immature but I'm not sure what would be the ideal approach. On one hand, you want to handle custom context and not show unnecessary errors, but on the other hand you do want 404 on urls that really don't exist in your application. Kalle > On Mon, Jun 7, 2010 at 12:50 PM, Kalle Korhonen > <kalle.o.korho...@gmail.com>wrote: > >> Use a Start page instead of an Index page - the index page treats >> everything as the context for the Index page if the string doesn't map >> to any other page. >> >> Kalle >> >> >> On Mon, Jun 7, 2010 at 9:43 AM, Todd Orr <torr0...@gmail.com> wrote: >> > I've setup a custom 404 page according to >> > >> http://wiki.apache.org/tapestry/Tapestry5HowToUseTapestryForCustomErrorPages >> . >> > However, whenever I navigate to a URL that does not exist Tapestry simply >> > renders the index page for that directory or a directory above if none >> > exists in that directory. How do you force Tapestry to use a custom 404? >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
