Kevin Menard wrote:
What we (or at least I) want is to deal with this at the page class level. The idea would be a page class can either be marked as secure or not and the framework would then take care of rewriting URLs with the appropriate scheme. Such a system would allow for a nice hierarchy of secure pages and likewise would cut down on the human error element by letting the framework do most of the grunt work.
This sounds like exactly what I need. I've raised the issue in Jira (http://issues.apache.org/jira/browse/TAPESTRY-991).
Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
