Just to be safe, could you create a JIRA issue for this? Then it won't go unnoticed.
Martijn On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote: > Hi, > > I've just upgraded my 1.3 beta 1 version to a personnally build > snapshot version based on revision xxx to fix a problem related to > Ajax and Page Expired, and the problem I had before is gone. Great! > > But now I've another strange problem. I get the following error message: > 18:49:19.245 [btpool0-2] ERROR org.apache.wicket.RequestCycle - The > component(s) below failed to render. A common problem is that you have > added a component in code but forgot to reference it in the markup > (thus the component will never be rendered). > > 1. [MarkupContainer [Component id = progressBarStylesheet, page = > org.xoocode.xooctory.web.pages.dashboard.Dashboard, path = > 2:projects-panel:projects:6:leftTimePanel:progressBar:progressBarStylesheet.StyleSheetReference, > isVisible = true, isVersioned = false]] > > The problem is that the component is properly added, and it worked > before upgrading, so... > > So I've tried to track down the problem, and I've not found the source > of the problem. As a workaround I disable check rendering with: > getDebugSettings().setComponentUseCheck(false); > Then everything works properly, and the component (a style sheet) is > properly rendered. > > Let me explain a little bit more the situation in which the problem occurs. > The component which is causing the problem is a StyleSheetReference > added to a panel. The markup contains the corresponding link in a > wicket:head section. > The panel is invisible when the page is loaded, but then I use an ajax > link to trigger an action, which later triggers the visibility of this > component to true. Then this component is refreshed by an AjaxTimer > (actually I use wicket-contrib-push, but I don't think it really makes > a difference, since it's using a simple AbstractAjaxTimerBehavior > underneath). And that's when the component is rendered that the check > rendering is failing. Some analysis shown that there's a > StyleSheetReference with the good id in the renderedComponent > attribute of Page, but it isn't the exact same StyleSheetReference > instance as the one checked by the checkRendering method. For the > moment I haven't managed to really see why I have two instances, what > doesn't help is that it seems that when I debug, the problem goes away > depending on the occurence of other timer based ajax requests. > > Do any of you have already faced this problem, or has any idea of how > it could come from? > > Xavier > > -- > Xavier Hanin - Independent Java Consultant > Manage your dependencies with Ivy! > http://incubator.apache.org/ivy/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > -- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
