Hi, In Wicket 6.0 there is no 'script' to decorate any more so IAjaxCallDecorator is not needed anymore. There is a replacement - IAjaxCallListener. Each AjaxBehavior can have a list of IACL and each of them can contribute: - before handler - JS to execute before the Ajax call is fired - after handler - JS to execute after the Ajax call is fired (when the call is asynchronous), or at the very end (after complete handlers) when synchronous - success handler - JS to execute when the Ajax call is successful - failure handler - JS to execute when the Ajax call is unsuccessful - complete handler - JS to execute when the Ajax call is either successful or unsuccessful
My question is: should we try to "translate" IAjaxCallDecorator to IAjaxCallListener or we should drop IACD completely ? The migration page will describe to do the "translation" in any case! Currently there is automatic delegation for the deprecated org.apache.wicket.ajax.AbstractDefaultAjaxBehavior#getChannel, org.apache.wicket.ajax.AbstractDefaultAjaxBehavior#getPreconditionScript, org.apache.wicket.ajax.AbstractDefaultAjaxBehavior#getFailureScript and org.apache.wicket.ajax.AbstractDefaultAjaxBehavior#getSuccessScript which are now moved to AjaxRequestAttributes. These methods will be removed in Wicket 7.0. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
