I like using classes, as you say it makes it re-factor proof.
This is in-fact what Wicket does too.
Thiago H. de Paula Figueiredo wrote:
Em Sun, 26 Oct 2008 06:39:21 -0300, Joel Halbert
<[EMAIL PROTECTED]> escreveu:
Is possible to reference pages by logical id rather than by path?
i.e. I would like to be able to reference a page like this:
t:page="name:editimages" rather than
t:page="manage/inventory/images/Edit"
I don't think so. Other option would be the page paramameter from
PageLink to also accept Class instances. We would have
refactoring-proof PageLink usage. It would be something like this:
t:page="prop:nextPage"
public Class getNextPage() {
return NextPage.class;
}
You can easily add a new "name" parameter binding to do what you want.
You can follow this example from the Tapestry wiki:
http://wiki.apache.org/tapestry/Tapestry5HowToAddMapBindingPrefix and
use a properties file to store the name/page mappings.
Hurray for Tapestry flexibility! :)
--
SU3 Analytics Ltd
61b Oxford Gardens
W10 5UJ
London
Tel: +44 20 8960 2634
Mob: +44 75 2501 0825
www.su3analytics.com
SU3 Analytics Ltd is a company registered in England and Wales under company
number 06639473 at registered address 61b Oxford Gardens, London W10 5UJ,
United Kingdom.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
