Damn it! I was this close holds fingers a hair-width apart.
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
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
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
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 authorization
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
