I'll try it today.

On 9/14/05, Simon Berriman <[EMAIL PROTECTED]> wrote:
Are you using Tomcat?  I had a similar problem with the examples between b3 and b4, and in the end it turned out to be the contents of Tomcat's 'work' directory.  (It only may be a Tomcat on Windows thing, maybe not.)  Stop Tomcat, delete the 'wicket-examples' directory under Tomcat's 'work' directory and try again.

hth,
-S.

________________________________

From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Nick Heudecker
Sent: 13 September 2005 16:37
To: [email protected]
Subject: [Wicket-user] RC1 Breaks DatePicker - Bayesian Filter detected spam


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?




















Come visit us at:

Content Management Europe Exhibition.  29th November - 1st December 2005, Olympia Grand Hall, London.  Stand # 341

GOSS - Ranked 4th in the Deloitte Technology Fast 50 Awards 2004 and 88th in the Deloitte Technology Fast 500 EMEA.

This email contains proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this email.



Email transmission cannot be guaranteed to be secure or error free, as information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. This email and any files attached to it have been checked with virus detection software before transmission. You should nonetheless carry out your own virus check before opening any attachment. GOSS Interactive Ltd accepts no liability for any loss or damage that may be caused by software viruses.




-------------------------------------------------------
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

Reply via email to