You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Stephane <sd...@cariboo-networks.com> on 2008/03/11 14:07:46 UTC
Article on the Tapestry Wiki
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
Re: Article on the Tapestry Wiki
Posted by Angelo Chen <an...@yahoo.com.hk>.
Hi Chris,
I do like to see your updated wiki, there are quite a number of wiki
articles that need to be either updated or remove considering t5 already
reach 5.0.11, however the dispatcher article still works as of now, in fact,
the ideas might be merged into a sub module, say, Tapestry-access or
something else, Tapestry-Hibernate, Tapestry-upload are modules i used a
lot, maybe Tapestry-Access in the future?
A.C.
Chris Lewis-5 wrote:
>
> A couple of quick points:
>
> I specifically avoid using annotations to mark pages as protected
> because I want the option of modifying permissions at runtime. Therefore
> the access controller would use a delegate to provide the matrix of
> pages names to role/user permissions. If you've read the dispatcher
>
>
--
View this message in context: http://www.nabble.com/Article-on-the-Tapestry-Wiki-tp15981665p16004840.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Article on the Tapestry Wiki
Posted by Chris Lewis <ch...@bellsouth.net>.
A couple of quick points:
I specifically avoid using annotations to mark pages as protected
because I want the option of modifying permissions at runtime. Therefore
the access controller would use a delegate to provide the matrix of
pages names to role/user permissions. If you've read the dispatcher
articles then you are aware that I left that part out entirely. I'd like
to update the article to include such an example, but I haven't yet
found the time. Actually I'd like to write a replacement article that
removes the need to parse the URL and uses T5 to provide the page
instance (and therefore the page name) automatically - cleaner, and
much safer.
Regarding your suggestion about a parameter to @Private - I haven't used
(and won't) acegi which means I haven't used tapestry-acegi, but that
system also uses an annotation to secure pages. That annotation takes a
parameter that indicates the 'role' required to access the page, which I
believe is what you want. I don't know if that's provided by
tapestry-acegi or acegi, but it's a model you can follow.
good luck
chris
Angelo Chen wrote:
> 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
>>
>>
>>
>
>
Re: Article on the Tapestry Wiki
Posted by Peter Stavrinides <p....@albourne.com>.
This is an interesting approach, I found the access controller Chris
wrote a great starting point... but I use the inverse approach to
Stephanie by protecting everything by default, but we are developing an
extranet though which is a slightly different implementation. The
annotations are a nice touch!
Peter
Stephane Decleire wrote:
> 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
>>>
>>>
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Article on the Tapestry Wiki
Posted by Stephane Decleire <sd...@cariboo-networks.com>.
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
>>
>>
>>
>
>
Re: Article on the Tapestry Wiki
Posted by Angelo Chen <an...@yahoo.com.hk>.
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
>
>
--
View this message in context: http://www.nabble.com/Article-on-the-Tapestry-Wiki-tp15981665p15995541.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Article on the Tapestry Wiki
Posted by Marcelo Lotif <ml...@gmail.com>.
It's here:
http://wiki.apache.org/tapestry/StephaneDecleire
the name of the page should be the name of the article...
2008/3/11, Chris Lewis <ch...@bellsouth.net>:
>
> Hi Stephane,
>
> I'd love to have a look, especially since I've found a seemingly better
> method of doing this (thanks to information from HLS). Unfortunately I
> can't access the page - perhaps the page name is wrong? The link points
> to: http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess, but
> that doesn't exist.
>
> chris
>
>
> Stephane 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
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Atenciosamente,
Marcelo Lotif
Re: Article on the Tapestry Wiki
Posted by Stephane <sd...@cariboo-networks.com>.
Sorry for the link ...
I've just made the correction.
Stephane
Chris Lewis a écrit :
> Hi Stephane,
>
> I'd love to have a look, especially since I've found a seemingly better
> method of doing this (thanks to information from HLS). Unfortunately I
> can't access the page - perhaps the page name is wrong? The link points
> to: http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess, but
> that doesn't exist.
>
> chris
>
> Stephane 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
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Article on the Tapestry Wiki
Posted by Chris Lewis <ch...@bellsouth.net>.
Hi Stephane,
I'd love to have a look, especially since I've found a seemingly better
method of doing this (thanks to information from HLS). Unfortunately I
can't access the page - perhaps the page name is wrong? The link points
to: http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess, but
that doesn't exist.
chris
Stephane 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org