If wicket policy prohibits isVisible() to depend on parent page, you might as well make it final. This is acceptable if you provide some other hook that may depend on parent page.
Johan Compagner wrote: > > Moreover, this is an inconsistent behavior. System should have the > same > behavior regardless whether log is enabled or not. > > > thats true, i was just saying your isVisible() shouldn't absolutely > depend on a parent page.. > It could be used in none logging code also. The parent hierarchy > doesn't have to be there > in specific cases (that we tried to solve in the now dead branch 2.0) > > johan > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
