Hi, I agree with you Howard that this is closely related to the requirement
to load templates from a db, which is still an interesting concept for
heavily CMS driven sites.
Is it too much to ask that, at least for pages, the template locator logic
could be delegated to the page class itself?!
For example, take a Product page with url /product/12345, and then the
requirement to override this page specifically for product 12345 but not
others. Then the page class could look something like:
@PageActivationContext
private long productId
public Resource getTemplate() {
return cmsResourceLocator.find(productId);
}
Maybe this starts to look a little MVC-like though.
Regards, Alfie.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Cache-keys-for-page-based-objects-tp3249337p3274735.html
Sent from the Tapestry - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
