On Sun, Jan 27, 2013 at 10:16 AM, Massimo Lusetti <mluse...@gmail.com>wrote:

> I'm interested in implementing the handling of requests to nonexistent
> pages.
> How do you handle requests to page that actually don't exists in your
> tapestry5 applications?
>

My typical pattern is don't use Index pages, use servlet standard error
code mapping to Tapestry error pages, e.g:

    <error-page>
        <error-code>401</error-code>
        <location>/error401</location>
    </error-page>
    <error-page>
        <error-code>404</error-code>
        <location>/error404</location>
    </error-page>

I use Tynamo's tapestry-routing (http://tynamo.org/tapestry-routing+guide)
for "folder-specific" index pages, e.g:
@At("/")
public class Home {...}

I've always found Tapestry's Index page handing to be too far reaching.

Kalle

Reply via email to