On 2/19/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > at least if in devel mode you should log a warning if you detect this. or do > you not detect its in a constructor...you just push a new target?
Why? If users want to do that, let them. Though it's probably not the smartest thing to do, there's nothing wrong with it either. If you want to log, you should log when a request target is pushed on top of an existing one. If you're worried about efficiency or something, that's a thing you probably never really need, though throwing exceptions around isn't the most elegant thing either. I don't see the problem anyway. I don't really see a good use case for it, but like I said, there is absolutely no reason why calling setResponsePage in the constructor is 'wrong' from an end user's perspective. Go ahead making improvements if you feel like it. I'm ok with how it is now. 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
