> can you show us your code?
> ...
> ah, sorry. this is the code i take it. just not in response to my
> original post (at least on nabble).
There is possibly an even simpler solution using onAttach - overriding
it in WebPage:
onAttach()
{
commonInit();
init();
}
public void init()
{
// developers can override this in their own pages to perform
// any post construction initialization
}
With this solution RequestCycle and BookmarkablePageRequestTarget don't
need to be touched.
Possible issues with the onAttach option:
1. The commonInit might not get called until a little later than it does
with the original option.
2. Users still have to remember to call super.onAttach in their
overridden handlers though this could be rectified by creating a new
method internalOnAttach that only the framework calls:
public void internalOnAttach()
{
if ( !inited )
commonInit();
onAttach();
}
For some reason the first option 'feels more elegant' because it remains
independent of the 'attach' phase of the lifecycle. There may be issues
with coupling the init and the attach phases of the lifecycle together
like that.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
