Filip S. Adamsen-2 wrote:
>
> If you implement PageRenderRequestFilter and ComponentEventRequestFilter
>
This looks very promising - I have two of the three needed elements
available (page, event name). At what point does the session attach and my
@ApplicationState get attached? Currently the logged in user is attached in
that fashion. Is there an alternative approach to keep track of who is
logged in that would be visible at the time the ComponentEventRequestFilter
is invoked?
Here is how the user is currently being registered:
(in my base page)
@ApplictionState
private User loggedInUser;
And here is how I'm registering the filter:
public void contributeComponentActionRequestHandler(
OrderedConfiguration<ComponentEventRequestFilter> configuration,
ComponentClassResolver componentClassResolver)
{
configuration.add("MyComponentEventRequestFilter",
new
SecureComponentEventRequestFilter(componentClassResolver), "after:*");
}
Filip S. Adamsen-2 wrote:
>
> To get at the page class from the handle method, use the ComponentSource
> service's getPage(String) method with the page name retrieved from the
> parameters passed to the handler methods.
>
For some reason my ComponentSource is null when the filter's handle method
is invoked. I'm trying to get the service by doing the following in my
ComponentEventRequestFilter:
@Inject
ComponentSource componentSource;
Thank you very much for your response!
--
View this message in context:
http://www.nabble.com/Can-a-page-do-something-before-actions-are-invoked-on-it--tp15509207p15549062.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
