it is pretty much the first thing that is called when that page is
touched. (in the responds)
If you are talking about the request process (so invoking a interface)
can be done on completely other pages.
then a response can be set. And then the page is first touched.
Are you saying you also want a checkAccess() call in the request cycle?
Before an interface is invoked?
Normally an invoke can't happen for a page where you don't have access
to because a render of the page should always be first
(else you can't target it anymore, you don't have any links to that page)
johan
Brian Xiang wrote:
Hi all,
I am pretty new to the Wicket framework. While I am looking at the
SignIn example, I found the Page.checkAccess() was called by
Page.onRender(), which I believe it is at pretty late stage of the
request process cycle, and lots of the business logic might have gone
through during WebrequstCycle.parseRequest(). Would this be a security
problem? Maybe I am missing something on the requst lifecycle.
Thanks,
Brian
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
