but it does look like this bug wicket-Bugs-1289771
It seems that for multiply components header contributions are added more then once now (or somethink like that)
On 9/14/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
But the forminput example does work for me.
Juergen
On 9/14/05, Johan Compagner <[EMAIL PROTECTED]> wrote:
> that seems like things that should be added to the head.
> So i think something goes wrong with that.
>
> With a single datepicker also fails? What does fail then? You can't
> input/submit the value?
>
> Can you open a bug report for this?
>
>
>
> On 9/13/05, Nick Heudecker <[EMAIL PROTECTED]> wrote:
> > Once we updated to the rc1 jars for Wicket and Extensions, the DatePicker
> no longer renders. We get the following Wicket exception:
> >
> >
> >
> > wicket.WicketRuntimeException: The component(s) below failed to render:
> >
> > 1. [MarkupContainer [Component id = calendarMain, page =
> pages.events.EditEvent, path =
> 13:border:eventForm:endDatePicker:calendarMain._javascript_Reference,
> isVisible = true, isVersioned = true]]
> > 2. [MarkupContainer [Component id = calendarSetup, page =
> pages.events.EditEvent, path =
> 13:border:eventForm:endDatePicker:calendarSetup._javascript_Reference,
> isVisible = true, isVersioned = true]]
> > 3. [MarkupContainer [Component id = calendarLanguage, page =
> pages.events.EditEvent, path =
> 13:border:eventForm:endDatePicker:calendarLanguage._javascript_Reference,
> isVisible = true, isVersioned = true]]
> > 4. [MarkupContainer [Component id = calendarStyle, page =
> pages.events.EditEvent, path =
> 13:border:eventForm:endDatePicker:calendarStyle.StyleSheetReference,
> isVisible = true, isVersioned = true]]
> >
> > at wicket.Page.checkRendering(Page.java :966)
> > at wicket.Page.doRender(Page.java:253)
> > at
> wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:219)
> > at wicket.RequestCycle.respond(RequestCycle.java:852)
> > at wicket.RequestCycle.request(RequestCycle.java:404)
> > at
> wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:195)
> > at javax.servlet.http.HttpServlet.service
> ( HttpServlet.java:689)
> > at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)The
> page in question has two DatePickers, but pages with a single date picker
> also fail to work, they just don't throw an exception. I thought this might
> be related to bug 1284029, but adjusting the url-mapping in the web.xml
> didn't fix it.
> >
> > The worked fine with b4 as the root servlet. Any ideas?
> >
> >
>
>
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
