It has to be done different way. you can do it with onsuccess
callback. This might be a bit tricky with current ajax implementation,
it will be much easier in Wicket 1.5
-Matej
On Tue, Sep 9, 2008 at 12:16 AM, Nino Saturnino Martinez Vazquez Wael
<[EMAIL PROTECTED]> wrote:
> Hi
>
> Im doing a mootip integration for wicketstuff (minis). I am only one step
> away from being able to release. Im having a bit of a problem with the ajax
> integration, might be me that have stared myself blind...
>
> This is where im at (I have all the other bits in place):
>
> var
> content=wicketAjaxGet('?wicket:interface=:0:tooltip02::IBehaviorListener:1:',
> null, null,null);
> content=document.getElementById('mooTipContent').innerHTML;
> return content;
>
> Now what happens are that the tooltip displays the previous tooltip, so it's
> always lacking one behind. It's because wicketAjaxGet loads asynchronous so
> the method returns content from the previous request.. So the question are
> is there anyway of waiting for wicketAjaxGet to complete? Or should it be
> done in another way?
>
> --
> -Wicket for love
>
> Nino Martinez Wael
> Java Specialist @ Jayway DK
> http://www.jayway.dk
> +45 2936 7684
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
