Forget about it. It does only apply if a Component implements IComponentResolver to resolve the component (ususally to check the parent as well like HtmlHeaderComponent and BodyOnLoadComponent which are transparent to the user) and than render it. If implemented by a registered component resolver (application.getComponentResolver().add(..)) it is up the component resolver what to do with the component found (e.g. autoAdd). It is unknown upfornt.
Juergen On 12/26/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > I'd like to change the signature of IComponentResolver.resolve(). > Currently the implementation has to resolve the component AND to > render it if found and returns true/false. IMO that is misleading > (resolveAndRender). I'd like to change it and return the Component > found. Though probably not many users have implemented there own > resolvers, it requires a change to the public API . Any objections > that I make this change? > > 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-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
