Of course, as i say on the wiki, to keep the sample simple, i have
defined the status of the user to be "logged in" or "logged out" but one
or several parameters can easily added to the annotation to define
several level of authentification !
Stephane
Angelo Chen a écrit :
Hi Stephane,
I have used Chris Lewis approach and it works very well, I put a list of
page names in the access control. looking at your annotation based approach,
i found it better, one thing I'd like to suggest is, there are two kind of
pages namely: A) pages that requires user to log in, B) pages that in
addition to A, it should be visible to the particular logged in user only.
maybe we can add a parameter to the @Private? thanks,
A.C.
Stephane Decleire wrote:
Hi,
I've just published an article on the Tapestry Wiki on how to implement
an access controller based on the dispatcher solution written by Chris
Lewis.
Feel free to comment and correct my poor english ;-)
Stephane
