Hi,

One of the bigger changes Wicket 5 and 6 is in wicket-ajax.js.
Part of the changes include improvements in FunctionsExecuter which causes
you problems.

Additionally Wicket optimizes the amount of "steps" the FunctionsExecuter
does by minimizing the number of <evaluate> elements in the Ajax response.
Less steps => smaller chance of stack overflow errors. The related ticket
is https://issues.apache.org/jira/browse/WICKET-4881



On Thu, Apr 25, 2013 at 11:51 AM, M4xime <maxime.nou...@capgemini.com>wrote:

> Hi,
>
> thanks for your reply.
>
> The problem is that there is a wicket upgrade scheduled in...2014.
>
> So, i have to find something to show to my client so that he understands
> why
> ie64 must not be used before the upgrade.
>
> I searched wicket's JIRA but i did not find any issue about my problem.
>
> Can you send me a link to an issue/release note that indicates that this
> part of the code has been refactored/fixed ?
>
> Thanks a lot !
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-9-StackOverflow-wicket-ajax-js-with-IE8-64bits-tp4658229p4658263.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com <http://jweekend.com/>

Reply via email to