> protected void onRenderHeadInitContribution(final Response > response) > protected void onRenderHeadContribution(final Response response)
The *original* idea behind that - stale since HeaderContributor was implemented - was that you need a contribution for the 'type', e.g. one dojo/ scriptaculous/ wicket-ajax contribution for 1-n dojo/ scriptaculous/ wicket-ajax based components, and that you need a header contribution for each separate component instance. That idea is stale because if you use HeaderContributor, the filtering is done for you so it is merely a matter of implementing equals/ hashcode properly on the header contributors. It was always my idea to refactor the ajax business to use HeaderContributor instead. That would have been way more elegant. This new idea has the advantage that it doesn't need to be added as behaviors, thus saving session state. Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
