Nevermind, looks like Andreas and Thomas answered your question.
Although I have to say that overriding the page names in your
hivemodule file seems like a cleaner approach than "hiding" the
default pages in your .application. My guess is that you were running
into a page resolution issue in your first attempt and Tapestry
couldn't find your custom pages (?). I'll find out for myself soon
enough since I have to do the same thing in a week or two...
-Ryan
On Oct 19, 2006, at 9:08 AM, Mats Henricson wrote:
Hi!
I've spent too much time trying to figure out how this is done in
Tapestry
4.
I found this suggestion on the net:
<contribution configuration-id="tapestry.InfrastructureOverrides">
<property name="exceptionPageName" value="GeneralError"/>
<property name="staleSessionPageName"
value="StaleSessionError"/>
<property name="staleLinkPageName" value="StaleLinkError"/>
</contribution>
The exception page works fine, but the stale session/link does not.
Does the accompanying Java page file need to extend a specific base?
I need no dynamic info displayed on my stale pages, just static text,
so I'd assume it would be a no-brainer.
Any suggestion?
Mats
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
