[
https://issues.apache.org/jira/browse/WICKET-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rodrigo De Castro updated WICKET-2437:
--------------------------------------
Fix Version/s: (was: 1.4-RC3)
(was: 1.3.6)
Description:
I have several lazy load panel that load DynamicImageResource objects. They are
always loaded in serial mode. These are the debug messages:
INFO: Initiating Ajax GET request on
../?wicket:interface=:3:tabpanel:panel:app_graph_panel:1:graph::IBehaviorListener:0:1&random=0.7774967316771
INFO: Invoking pre-call handler(s)...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Channel busy - postponing...
INFO: Received ajax response (2665 characters)
was:
The loading process of an image which loads its contents from a
DynamicImageResource blocks changing of an AjazLazyLoadPanel from indicating
image to content. "respond(...)" method of AbstractDefaultAjaxBehavior from
AjaxLazyLoadPanel is never called.
Within the attached quick start there is a forced delay because the image is
too small and loads too quick to force the error. I think the problem is that
loading the first dynamic resource changes state of the page from "domready" to
"load" and attached AjaxLazyLoadPanel script ignores it's execution.
Affects Version/s: (was: 1.3.5)
1.4.0
> DynamicImageResource images are loaded in serial mode (Channel busy -
> postponing...)
> ------------------------------------------------------------------------------------
>
> Key: WICKET-2437
> URL: https://issues.apache.org/jira/browse/WICKET-2437
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.4.0
> Reporter: Rodrigo De Castro
> Assignee: Matej Knopp
>
> I have several lazy load panel that load DynamicImageResource objects. They
> are always loaded in serial mode. These are the debug messages:
> INFO: Initiating Ajax GET request on
> ../?wicket:interface=:3:tabpanel:panel:app_graph_panel:1:graph::IBehaviorListener:0:1&random=0.7774967316771
> INFO: Invoking pre-call handler(s)...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Received ajax response (2665 characters)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
