Damn it! I was this close .
I modified my MetaDataComponentProtector class (very close to the
MetaDataRoleAuthorizationStrategy, but I need to store a Predicate
(commons-collections) with the action for dynamic evaluation) to be an
IAuthorizationStrategy removed the onBeforeRender and it worke
> I went through all that not only for your benefit :), but also because I
> have a question. Currently, when I mark a component as protected, I add the
> Component to a List on the Page (protectedComponents) so that onBeforeRender
> doesn't have to go to every child Compoennt of the page (which c
Eelco Hillenius wrote:
>
>> Attempting to play with the application or Session AuthorizationStrategy
>> doesn't seem to be a good idea because it I would need to somehow inject
>> the
>> current page into the "Authorization Process".
>
> I think you are trying too hard to fit the existing autho
> Attempting to play with the application or Session AuthorizationStrategy
> doesn't seem to be a good idea because it I would need to somehow inject the
> current page into the "Authorization Process".
I think you are trying too hard to fit the existing authorization
strategies, which in fact are
OK, so narrowing down my thought process...
Attempting to play with the application or Session AuthorizationStrategy
doesn't seem to be a good idea because it I would need to somehow inject the
current page into the "Authorization Process".
So, I am back to adding the AuthorizationStrategy to
I am using the RoleAuthorizationStrategy (which uses
MetaDataRoleAuthorizationStrategyinternally) in my app and it works fine. I
have a user object that has a list of valid roles in the application.
What I want to do now is make my pages role-based. For example, if you are
an originator, you wo
