[
https://issues.apache.org/jira/browse/WICKET-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462598#comment-13462598
]
Martin Grigorov commented on WICKET-4470:
-----------------------------------------
It seems you need stable channel names. Each lazy load panel should use the
same channel name as the Ajax behavior(s) in that panel. The channel type
should be ACTIVE, i.e. until the lazy load panel fully loads no Ajax behavior
should be executed on it and its children.
> problem with loading lazy components
> ------------------------------------
>
> Key: WICKET-4470
> URL: https://issues.apache.org/jira/browse/WICKET-4470
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.5
> Reporter: Michal Wegrzyn
> Attachments: myproject.zip, myproject.zip
>
>
> It seems that probably WICKET-4227 is not fixed. I am still getting problems
> in 1.5.5.
> If I override ajax channel like:
> @Override
> protected AjaxChannel getChannel() {
> return new AjaxChannel( "0", AjaxChannel.Type.DROP ); }
> Only last item is loaded and other items are in continuous loading state -
> see WICKET-4397.
> With unique channel name:
> @Override
> protected AjaxChannel getChannel() {
> return new AjaxChannel( String.valueOf( System.currentTimeMillis() ),
> AjaxChannel.Type.DROP ); }
> lazy items are loaded asynchronously, however if I try to do action which
> results in drop, I am getting the same exception as in WICKET-4227.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
