sync doesnt help in the area one bit
Because wicket already does that for you
The problem is that just after 1 ajax call that replaces/removes/what ever a
component another 1 is already waiting and want to execute.
in 1.5 we have to have a hash instead of the id i guess and silent failure
when the behavior is gone
But matej is working on that so everything will be great
johan
On Sat, Sep 27, 2008 at 3:16 AM, Adriano dos Santos Fernandes <
[EMAIL PROTECTED]> wrote:
> Nino Saturnino Martinez Vazquez Wael wrote:
>
>> Hi Guys
>>
>> One of the major problems with the game are that if you click a
>> box(AjaxEventBehavior) while the heartbeat(AbstractAjaxTimerBehavior) are in
>> process you will get an error, since the box's component has changed and no
>> longer carries that behavior. I've tried to solve this by adding a
>> transparent veil to the page once the heartbeat processes, it's simply not
>> good enough, it's still possible to get errors. So how do I solve this?
>>
>> I have one idea but im not liking it, all box's could have behaviors even
>> if you wont get an score, that way we will not get an error.
>>
>>
>> This is a potential pitfall if you ever will have two Ajax components that
>> can remove the ones behavior, if the user clicks the other while loading
>> then it's gonna complain. On the other hand im not sure what wicket can do
>> besides throw a runtime exception.
>>
>> Can't you use synchronized (obj) { ... }, to serialize multiple threads
> of each ajax call?
>
>
> Adriano
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
