i wouldn't do page initialisation in another place then the consrtuctor or maybe do it in checkaccess only i cant tell at the moment if that is to late (you cant change the structure of the page in the render phase)
if you want to check access before an initialised page i think you have to use a factory for that. so every where you create a page call a factory that creates the page for you Wicket in the 1.2 stream also now has (or beginning to have) security feattures you can look at. wat is in youre place the deciding factor which page can be viewed/created? Is it just the page class name? On 11/26/05, Iman RahmatiZadeh <[EMAIL PROTECTED]> wrote: > I've ran into these questions many times, working with checkAccess(), > Spring > integration, etc. Just wondering if anybody has come up with some good > idea's : > > 1 - What's the best method for doing page initilization outside the page > constructor ? Is overriding onBeginRequest() and adding components there a > good idea ? > > 2- checkAccess() (and login) happen after the Page has been created. Is > there any better way to check access before instantiating the whole page ? > Like maybe some sort of access control before calling the page factory ? > > Iman > > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
