On 12/22/05, Johan Compagner <[EMAIL PROTECTED]> wrote: > for the component itself we already do that: > // Component is removed > component.setParent(null); > > But ofcourse this could not be the case that the component itself is not > removed but a parent of it and he is reused instead of its parent. > But this is pretty far fetched don't think this will happen a lot. >
I agree and because it is far fetched I'd prefer to throw an exception and provide a clear error message to the user. Juergen ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
