The fix should be in SVN. But there is a bug in 1.2 now that prevents
rendering datepicker in ajax response, so I wouldn't recommend updating
right now.
In the meanwhile you can try to disable ajax debug, it should help.
( getAjaxSettings().setAjaxDebugModeEnabled(false) ).
-Matej
Iuly wrote:
Would you mind sharing some of that code? And open up a bug report
please? It probably has to do with last week's refactorings of header
contributions. Sorry it broke your app, you're probably best off
rolling back to 1.2.1 until we fix this.
Thanks,
Eelco
On 8/31/06, Iuly <[EMAIL PROTECTED]> w
Thanks for the reply.
I will detail below the ajax context and also component hierarchy involved.
So in my page I have a main container which extends Border component. I’ve
set on this container
setOutputMarkupId(true). Let’s name this container A.
Panel(extends Panel component) that contains D
I was trying to reproduce it by placing a datepicker on an ajax tab of
the ajax tabs example. But that works just fine and I can't get it to
stall.
I replied on another thread earlier. Would you mind describing which
components you use/ what your context is in that thread?
Eelco
On 8/31/06, Iuly
Yup I have experienced this same problem. Hope it get addressed soon before
our QA nails us down!
Iuly wrote:
>
> Hi,
> I've upgraded my current application to 1.2.2 wicket version. The only
> problem that occured is related to DatePicker.
> Shortly I have the following use case : if a panel
