You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Andreas Pardeike <ap...@fsys.se> on 2008/03/11 11:09:31 UTC
Page class annotations (was Re: Checking for a logged in user globally)
Great. One question though. I tried to create my own annotation Access
@PageAccess(Access.PUBLIC)
public class Start
{
...
}
but
Class<? extends Component> pageClass = page.getClass();
PageAccess access = pageClass.getAnnotation(PageAccess.class);
fails because there are no annotations in 'page'. What am I doing wrong?
/Andreas
On 10 mar 2008, at 20.20, Filip S. Adamsen wrote:
> Hi,
>
> The logical page name is available in the parameters passed to your
> filter. You can then use the ComponentSource to get at the actual
> class using the logical page name and extract whatever info you'd
> like - I use this service along with annotations on my page classes:
>
> public class PageAccessCheckerImpl
> implements PageAccessChecker {
>
> private final SecurityService securityService;
> private final ComponentSource componentSource;
>
> public PageAccessCheckerImpl(SecurityService securityService,
> ComponentSource componentSource) {
> this.securityService = securityService;
> this.componentSource = componentSource;
> }
>
> public void checkPageAccess(PageRenderRequestParameters parameters) {
> checkPageAccess(parameters.getLogicalPageName());
> }
>
> public void checkPageAccess(ComponentEventRequestParameters
> parameters) {
> checkPageAccess(parameters.getActivePageName());
> }
>
> private void checkPageAccess(String pageName) {
> Component page = componentSource.getPage(pageName);
> Secured secured = page.getClass().getAnnotation(Secured.class);
>
> if (null == secured) return;
> if (!securityService.isUserLoggedIn()) throw new
> LoginRequiredException();
> if (!securityService.isUserInRole(secured.value())) throw new
> AccessForbiddenException();
> }
> }
>
> I then handle the exceptions in my handlers and redirect to another
> page if necessary.
>
> -Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Page class annotations (was Re: Checking for a logged in user globally)
Posted by Andreas Pardeike <ap...@fsys.se>.
Filip,
After refactoring my code about a dozen times your suggestion (and
my original code) did the trick.
Thanks!
Andreas Pardeike
On 11 mar 2008, at 13.11, Filip S. Adamsen wrote:
> Cordenier, that's a VERY complicated way to get the class, when, in
> fact, getClass() on the Component returned by ComponentSource works
> just fine.
>
> So that's not the problem. No, I think Andreas forgot to add
> @Retention(RetentionPolicy.RUNTIME) to his annotation, simple as that.
>
> Hope this helps. :)
>
> -Filip
>
> Cordenier Christophe skrev:
>
>> To resolve the class of a component, you have to use the
>> "ComponentResources" class.
>> It contains the componentModel that allows you to the class of the
>> "coreComponent" by using the method "getComponentClassName".
>> With this method you can resolve the "Real" class of your component
>> or page.
>> There is also the ComponentClassResolver service that allows you to
>> access information on the component class.
>> Check for example the code of "PageElementFactoryImpl" that uses
>> this service to instantiate components.
>> -----Message d'origine-----
>> De : Andreas Pardeike [mailto:ap@fsys.se]
>> Envoyé : mardi 11 mars 2008 11:10
>> À : Tapestry users
>> Objet : Page class annotations (was Re: Checking for a logged in
>> user globally)
>> Great. One question though. I tried to create my own annotation
>> Access
>> @PageAccess(Access.PUBLIC)
>> public class Start
>> {
>> ...
>> }
>> but
>> Class<? extends Component> pageClass = page.getClass();
>> PageAccess access = pageClass.getAnnotation(PageAccess.class);
>> fails because there are no annotations in 'page'. What am I doing
>> wrong?
>> /Andreas
>> On 10 mar 2008, at 20.20, Filip S. Adamsen wrote:
>>
>>> Hi,
>>>
>>> The logical page name is available in the parameters passed to your
>>> filter. You can then use the ComponentSource to get at the actual
>>> class using the logical page name and extract whatever info you'd
>>> like - I use this service along with annotations on my page classes:
>>>
>>> public class PageAccessCheckerImpl
>>> implements PageAccessChecker {
>>>
>>> private final SecurityService securityService;
>>> private final ComponentSource componentSource;
>>>
>>> public PageAccessCheckerImpl(SecurityService securityService,
>>> ComponentSource componentSource) {
>>> this.securityService = securityService;
>>> this.componentSource = componentSource;
>>> }
>>>
>>> public void checkPageAccess(PageRenderRequestParameters
>>> parameters) {
>>> checkPageAccess(parameters.getLogicalPageName());
>>> }
>>>
>>> public void checkPageAccess(ComponentEventRequestParameters
>>> parameters) {
>>> checkPageAccess(parameters.getActivePageName());
>>> }
>>>
>>> private void checkPageAccess(String pageName) {
>>> Component page = componentSource.getPage(pageName);
>>> Secured secured = page.getClass().getAnnotation(Secured.class);
>>>
>>> if (null == secured) return;
>>> if (!securityService.isUserLoggedIn()) throw new
>>> LoginRequiredException();
>>> if (!securityService.isUserInRole(secured.value())) throw new
>>> AccessForbiddenException();
>>> }
>>> }
>>>
>>> I then handle the exceptions in my handlers and redirect to another
>>> page if necessary.
>>>
>>> -Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: Page class annotations (was Re: Checking for a logged in user
globally)
Posted by Cordenier Christophe <Ch...@atosorigin.com>.
Hi Filip,
You're right. I will not forget the advice.
I was thinking of the Page object when I answer the thread, sorry.
Not the "ComponentSource" service.
Christophe.
-----Message d'origine-----
De : Filip S. Adamsen [mailto:fsa@fsadev.com]
Envoyé : mardi 11 mars 2008 13:12
À : Tapestry users
Objet : Re: Page class annotations (was Re: Checking for a logged in user globally)
Hi,
Cordenier, that's a VERY complicated way to get the class, when, in
fact, getClass() on the Component returned by ComponentSource works just
fine.
So that's not the problem. No, I think Andreas forgot to add
@Retention(RetentionPolicy.RUNTIME) to his annotation, simple as that.
Hope this helps. :)
-Filip
Cordenier Christophe skrev:
> To resolve the class of a component, you have to use the "ComponentResources" class.
> It contains the componentModel that allows you to the class of the "coreComponent" by using the method "getComponentClassName".
>
> With this method you can resolve the "Real" class of your component or page.
>
> There is also the ComponentClassResolver service that allows you to access information on the component class.
>
> Check for example the code of "PageElementFactoryImpl" that uses this service to instantiate components.
>
> -----Message d'origine-----
> De : Andreas Pardeike [mailto:ap@fsys.se]
> Envoyé : mardi 11 mars 2008 11:10
> À : Tapestry users
> Objet : Page class annotations (was Re: Checking for a logged in user globally)
>
> Great. One question though. I tried to create my own annotation Access
>
> @PageAccess(Access.PUBLIC)
> public class Start
> {
> ...
> }
>
> but
>
> Class<? extends Component> pageClass = page.getClass();
> PageAccess access = pageClass.getAnnotation(PageAccess.class);
>
> fails because there are no annotations in 'page'. What am I doing wrong?
>
> /Andreas
>
>
> On 10 mar 2008, at 20.20, Filip S. Adamsen wrote:
>
>> Hi,
>>
>> The logical page name is available in the parameters passed to your
>> filter. You can then use the ComponentSource to get at the actual
>> class using the logical page name and extract whatever info you'd
>> like - I use this service along with annotations on my page classes:
>>
>> public class PageAccessCheckerImpl
>> implements PageAccessChecker {
>>
>> private final SecurityService securityService;
>> private final ComponentSource componentSource;
>>
>> public PageAccessCheckerImpl(SecurityService securityService,
>> ComponentSource componentSource) {
>> this.securityService = securityService;
>> this.componentSource = componentSource;
>> }
>>
>> public void checkPageAccess(PageRenderRequestParameters parameters) {
>> checkPageAccess(parameters.getLogicalPageName());
>> }
>>
>> public void checkPageAccess(ComponentEventRequestParameters
>> parameters) {
>> checkPageAccess(parameters.getActivePageName());
>> }
>>
>> private void checkPageAccess(String pageName) {
>> Component page = componentSource.getPage(pageName);
>> Secured secured = page.getClass().getAnnotation(Secured.class);
>>
>> if (null == secured) return;
>> if (!securityService.isUserLoggedIn()) throw new
>> LoginRequiredException();
>> if (!securityService.isUserInRole(secured.value())) throw new
>> AccessForbiddenException();
>> }
>> }
>>
>> I then handle the exceptions in my handlers and redirect to another
>> page if necessary.
>>
>> -Filip
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
>
> Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Page class annotations (was Re: Checking for a logged in user
globally)
Posted by "Filip S. Adamsen" <fs...@fsadev.com>.
Hi,
Cordenier, that's a VERY complicated way to get the class, when, in
fact, getClass() on the Component returned by ComponentSource works just
fine.
So that's not the problem. No, I think Andreas forgot to add
@Retention(RetentionPolicy.RUNTIME) to his annotation, simple as that.
Hope this helps. :)
-Filip
Cordenier Christophe skrev:
> To resolve the class of a component, you have to use the "ComponentResources" class.
> It contains the componentModel that allows you to the class of the "coreComponent" by using the method "getComponentClassName".
>
> With this method you can resolve the "Real" class of your component or page.
>
> There is also the ComponentClassResolver service that allows you to access information on the component class.
>
> Check for example the code of "PageElementFactoryImpl" that uses this service to instantiate components.
>
> -----Message d'origine-----
> De : Andreas Pardeike [mailto:ap@fsys.se]
> Envoyé : mardi 11 mars 2008 11:10
> À : Tapestry users
> Objet : Page class annotations (was Re: Checking for a logged in user globally)
>
> Great. One question though. I tried to create my own annotation Access
>
> @PageAccess(Access.PUBLIC)
> public class Start
> {
> ...
> }
>
> but
>
> Class<? extends Component> pageClass = page.getClass();
> PageAccess access = pageClass.getAnnotation(PageAccess.class);
>
> fails because there are no annotations in 'page'. What am I doing wrong?
>
> /Andreas
>
>
> On 10 mar 2008, at 20.20, Filip S. Adamsen wrote:
>
>> Hi,
>>
>> The logical page name is available in the parameters passed to your
>> filter. You can then use the ComponentSource to get at the actual
>> class using the logical page name and extract whatever info you'd
>> like - I use this service along with annotations on my page classes:
>>
>> public class PageAccessCheckerImpl
>> implements PageAccessChecker {
>>
>> private final SecurityService securityService;
>> private final ComponentSource componentSource;
>>
>> public PageAccessCheckerImpl(SecurityService securityService,
>> ComponentSource componentSource) {
>> this.securityService = securityService;
>> this.componentSource = componentSource;
>> }
>>
>> public void checkPageAccess(PageRenderRequestParameters parameters) {
>> checkPageAccess(parameters.getLogicalPageName());
>> }
>>
>> public void checkPageAccess(ComponentEventRequestParameters
>> parameters) {
>> checkPageAccess(parameters.getActivePageName());
>> }
>>
>> private void checkPageAccess(String pageName) {
>> Component page = componentSource.getPage(pageName);
>> Secured secured = page.getClass().getAnnotation(Secured.class);
>>
>> if (null == secured) return;
>> if (!securityService.isUserLoggedIn()) throw new
>> LoginRequiredException();
>> if (!securityService.isUserInRole(secured.value())) throw new
>> AccessForbiddenException();
>> }
>> }
>>
>> I then handle the exceptions in my handlers and redirect to another
>> page if necessary.
>>
>> -Filip
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
>
> Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: Page class annotations (was Re: Checking for a logged in user
globally)
Posted by Cordenier Christophe <Ch...@atosorigin.com>.
To resolve the class of a component, you have to use the "ComponentResources" class.
It contains the componentModel that allows you to the class of the "coreComponent" by using the method "getComponentClassName".
With this method you can resolve the "Real" class of your component or page.
There is also the ComponentClassResolver service that allows you to access information on the component class.
Check for example the code of "PageElementFactoryImpl" that uses this service to instantiate components.
-----Message d'origine-----
De : Andreas Pardeike [mailto:ap@fsys.se]
Envoyé : mardi 11 mars 2008 11:10
À : Tapestry users
Objet : Page class annotations (was Re: Checking for a logged in user globally)
Great. One question though. I tried to create my own annotation Access
@PageAccess(Access.PUBLIC)
public class Start
{
...
}
but
Class<? extends Component> pageClass = page.getClass();
PageAccess access = pageClass.getAnnotation(PageAccess.class);
fails because there are no annotations in 'page'. What am I doing wrong?
/Andreas
On 10 mar 2008, at 20.20, Filip S. Adamsen wrote:
> Hi,
>
> The logical page name is available in the parameters passed to your
> filter. You can then use the ComponentSource to get at the actual
> class using the logical page name and extract whatever info you'd
> like - I use this service along with annotations on my page classes:
>
> public class PageAccessCheckerImpl
> implements PageAccessChecker {
>
> private final SecurityService securityService;
> private final ComponentSource componentSource;
>
> public PageAccessCheckerImpl(SecurityService securityService,
> ComponentSource componentSource) {
> this.securityService = securityService;
> this.componentSource = componentSource;
> }
>
> public void checkPageAccess(PageRenderRequestParameters parameters) {
> checkPageAccess(parameters.getLogicalPageName());
> }
>
> public void checkPageAccess(ComponentEventRequestParameters
> parameters) {
> checkPageAccess(parameters.getActivePageName());
> }
>
> private void checkPageAccess(String pageName) {
> Component page = componentSource.getPage(pageName);
> Secured secured = page.getClass().getAnnotation(Secured.class);
>
> if (null == secured) return;
> if (!securityService.isUserLoggedIn()) throw new
> LoginRequiredException();
> if (!securityService.isUserInRole(secured.value())) throw new
> AccessForbiddenException();
> }
> }
>
> I then handle the exceptions in my handlers and redirect to another
> page if necessary.
>
> -Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org