You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martin Grigorov <mg...@apache.org> on 2012/01/03 17:29:31 UTC
What to do with IAjaxCallDecorator ?
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
Re: What to do with IAjaxCallDecorator ?
Posted by Igor Vaynberg <ig...@gmail.com>.
i have a couple of those to prepend js before the ajax call is made...
if we cant translate lets remove the iface so it causes a compile error
-igor
On Tue, Jan 3, 2012 at 9:07 AM, Martin Grigorov <mg...@apache.org> wrote:
> On Tue, Jan 3, 2012 at 6:57 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>> we cant translate decorateSript() can we?
>
> Not automatically.
> People need to put their old code either in before, after or both.
>
> I doubt anyone modified the 'script' parameter itself. This wont be
> supported in 6.0!
>
>>
>> -igor
>>
>> On Tue, Jan 3, 2012 at 8:29 AM, Martin Grigorov <mg...@apache.org> wrote:
>>> 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
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
Re: What to do with IAjaxCallDecorator ?
Posted by Martin Grigorov <mg...@apache.org>.
On Tue, Jan 3, 2012 at 6:57 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> we cant translate decorateSript() can we?
Not automatically.
People need to put their old code either in before, after or both.
I doubt anyone modified the 'script' parameter itself. This wont be
supported in 6.0!
>
> -igor
>
> On Tue, Jan 3, 2012 at 8:29 AM, Martin Grigorov <mg...@apache.org> wrote:
>> 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
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: What to do with IAjaxCallDecorator ?
Posted by Igor Vaynberg <ig...@gmail.com>.
we cant translate decorateSript() can we?
-igor
On Tue, Jan 3, 2012 at 8:29 AM, Martin Grigorov <mg...@apache.org> wrote:
> 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