On Mon, Oct 15, 2012 at 2:56 PM, Martin Grigorov <[email protected]> wrote: > Hi, > > On Mon, Oct 15, 2012 at 11:50 AM, Michael Zhavzharov > <[email protected]> wrote: >>>>>you'll need to acquire the page lock, i.e. you will face the same problem. >> >> i.e. there is no way to load components in page, showing loading indicator >> and give user an opportunity to work with another elements on page? > > There is. You need to use different names for the ajax channels of the > Ajax behaviors. > See org.apache.wicket.ajax.attributes.AjaxRequestAttributes#setChannel
This will remove the synchronization at the client side but to improve the blocking at the server side you will need to poll for the new state as Ernesto suggested. > >> >> Thank you for your concern. >> I don't know were to load app, that's why I loaded it to Google docs: >> allpProject.zip on google >> <https://docs.google.com/open?id=0BwHokpA1QcAkdGk2QmdrQ0RhUzQ> > > The solution is to remove id="ajaxPanel" from the markup. Just leave > wicket:id there. > >> >> >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Multiple-AjaxLazyLoadPanel-s-never-load-tp4652907p4652968.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
