The problem is that Wicket doesn't manage it's pages that way. The pagefactory is only used in certain cases, like page links and for bookmarkable pages. Good thing about not managing them is that it gives you greater flexibility and allows for an easier programming model (no need for abstract pages etc). The downside is that some things are harder/ impossible for the framework to do.
But let's see... There are actually three important phases of a page: construction, handling a component handler request and rendering a page. The callback you are looking for is the second one, right? Maybe combined with the first if that's doable. > I would rather like a similar method outside the pages, perhaps > IPageFactory.wakeUp(Page). > Eelco ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
