You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Matej Knopp (JIRA)" <ji...@apache.org> on 2007/03/15 15:42:09 UTC

[jira] Resolved: (WICKET-392) Collisions between 'seperate' wicketAjaxGet calls.

     [ https://issues.apache.org/jira/browse/WICKET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Knopp resolved WICKET-392.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3

> Collisions between 'seperate' wicketAjaxGet calls.
> --------------------------------------------------
>
>                 Key: WICKET-392
>                 URL: https://issues.apache.org/jira/browse/WICKET-392
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>         Environment: URL: https://svn.apache.org/repos/asf/incubator/wicket/branches/wicket-1.x
> Rev: 518376
>            Reporter: Martin Funk
>             Fix For: 1.3
>
>         Attachments: ChannelBusyBug.diff
>
>
> Two wicketAjaxGet calls collide if the second one is caled while the first one still processes the onSuccessScript.
> See attached QuickStartPatch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.