{
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Access-control-with-dispatchers-and-annotations-tp18710376p18768093.html
On Tue, Jul 29, 2008 at 3:54 PM, Sven Homburg [EMAIL PROTECTED] wrote:
massimo,
i ask me sometimes, now i ask you ;-)
why do you use the the Restriced annotation not directly
your code RestrictedWorker class seach for Restriced class an injected
some metas into the page/component
after
Could you try to move all non-page classes/interfaces out of the pages
package (same applies to components). So move Private.java to some
package other than in components, mixins, base, pages
Martijn
On Wed, 2008-07-30 at 10:41 +0100, [EMAIL PROTECTED] wrote:
I too have been trying to
Hi,
I'm trying to create an access control system using a dispatcher as
described on the wiki page.
I'm following this:
http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess
So that I can use an annotation to declare which pages need a logged-in
user.
It checks the meta-data in the
Hi,
I think there is a bug in the Wiki. Try this instead
Component page = componentSource.getPage(pageName);
Private prvAnnot = page.getClass().getAnnotation(
Private.class);
when your Annotation is called Private of course.
You'll get
On Tue, Jul 29, 2008 at 1:41 PM, Carl Crowder [EMAIL PROTECTED] wrote:
Hi,
I'm trying to create an access control system using a dispatcher as
described on the wiki page.
I'm following this:
http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess
So that I can use an annotation to
I've been trying to use the same code.
The problem lies apparently in the fact that the class returned by
getAnnotation is not Private but a proxy...
...
page anno class=$Proxy40
...
Quoting Moritz Gmelin [EMAIL PROTECTED]:
Hi,
I think there is a bug in the Wiki. Try this instead
massimo,
i ask me sometimes, now i ask you ;-)
why do you use the the Restriced annotation not directly
your code RestrictedWorker class seach for Restriced class an injected
some metas into the page/component
after that the AccessValidatorImpl ask for the private meta ???
why not directly work
Cheers for all the replies - I've taken Moritz's approach in the end :)
I've updated the wiki page to reflect this.
Carl
Moritz Gmelin wrote:
Hi,
I think there is a bug in the Wiki. Try this instead
Component page = componentSource.getPage(pageName);
Private prvAnnot =