On 3/5/07, Chris Lintz <[EMAIL PROTECTED]> wrote: > > I was hoping to prevent any one implementing the component from ever being > able to add more than one at development time by wrapping add() with > something like setComponent(). I guess I will have to lean on the method > below and fall back on run-time exceptions. > > Thanks. That is helpful although not ideal.
I agree that it is not very elegant. Igor and others, how about adding a protected non-final method like allowAdd or something? Eelco ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
