I think this a Spring-Security issue, not a Tapestry one. I never did
that but i think u may want to look at AccessDecisionVoter interface
and implement one that checks its value agains the database.
This may help u:
http://blog.springsource.com/2009/01/02/spring-security-customization-part-2-adju
On Sat, 16 Jan 2010 00:10:42 -0200, jc1001 wrote:
Is it possible to use dynamic roles in the @Secured("ROLE_XYZ") page
annotation in such a way that a service could be employed to retrieve a
list of roles and populate the annotation before the request is
intercepted/interrogate by the Sprin
Is it possible to use dynamic roles in the @Secured("ROLE_XYZ") page
annotation in such a way that a service could be employed to retrieve a list
of roles and populate the annotation before the request is
intercepted/interrogate by the Spring $ecurity integration? Something
equivalent to an expan
