I'm interested in implementing the handling of requests to nonexistent pages.
This is something that has to work nicely with the concept of "activation context" that tapestry5 has since day one. Now my solution would be to have the platform (tapestry5) to signal with a 404 error when it encounter a request to a nonexistent page or to a page with the wrong activation context parameter. Before going any further I would like to ask for suggestion on how you envision the situation or to know your experience in the fields. How do you handle requests to page that actually don't exists in your tapestry5 applications? Cheers -- Massimo
