Is there anyway you can leverage web.xml error handling for this?
<web-app>
...
<error-page>
<error-code>404</error-code>
<location>errors/FourOhFour.tml</location>
</error-page>
<error-page>
<exception-type>java.lang.Throwable</exception-type>
<location>errors/throwable.tml</location>
</error-page>
...
</web-app>
IE: catch *specific *exceptions (what is thrown for missing pages, etc) and
push them to a Tapestry page that implements the logic you want? Please
don't take the example literally :) i.e. handle whatever exceptions and
forward to whatever pages would make sense.
-Luther
On Thu, Mar 12, 2009 at 3:28 PM, Geoffrey Wiseman <
geoffrey.wise...@gmail.com> wrote:
> On Wed, Mar 11, 2009 at 7:33 PM, nillehammer
> <tapestry.nilleham...@winfonet.eu> wrote:
>
> > Tapestry's Delegate-Component
> > (
> >
> http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components/Delegate.html
> > )
> > to show an error message.
> >
>
> I guess I'm still processing this -- how would a delegate component be of
> help to me here?
> It's a little awkward to have each index template have a top-level
> conditional:
> - if this is a 'not found' then show an error
> - else show the actual page template
>
> I dunno how often I'd be repeating this pattern - perhaps very rarely. If
> it came up more than a couple times, I'd probably live with the
> /pagenotfound approach just to avoid the duplication. I suppose I could
> even use a layout to get around the duplication. Anyway -- ultimately, I
> think I'm probably fighting against the grain a little too hard and should
> probably just live with the /start URL and accept that Tapestry owns the
> URL
> structure more than I'd necessarily choose. ;)
>
> - Geoffrey
> --
> Geoffrey Wiseman
> http://www.geoffreywiseman.ca/
>
