Ok. If you really want to go ahead with page spec parsing i guess you
can use the servlet context to find the spec file and then you'll have
to parse it yourself. You can inject the servlet context adding this to
your pages base class:
@InjectObject("service:tapestry.globals.ServletContext")
public abstract ServletContext getServletContext();
Robert J. Walker wrote:
Yeah, we've been considering Acegi, but that's a little more long-range. The
only issue I have with using annotations for this is that I would have to
create a class for every page in the app. As it stands right now, I'm able to
reuse the same class for a fair number of my simpler pages without having a
subclass for each one.
Robert J. Walker
-----Original Message-----
From: Hugo Palma [mailto:[EMAIL PROTECTED]
Sent: Monday, January 29, 2007 4:53 PM
To: Tapestry users
Subject: Re: Reading page specifications... *without* loading the page
Without really answering your question, have you looked at
tapestry-acegi (http://www.carmanconsulting.com/tapestry-acegi/).
The Secured annotation is a life saver......
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
