Nevermind, error on my part.
On Mon, Nov 3, 2008 at 5:20 PM, Andrew Berman <[EMAIL PROTECTED]> wrote: > So even if I do this, all child pages need to add their components to the > body and not the direct page itself which to me doesn't seem right. Is > there a way to get around this or is there a better way to add a dynamic > class to the body tag? > > > On Fri, Oct 31, 2008 at 2:54 PM, Andrew Berman <[EMAIL PROTECTED]> wrote: > >> Awesome, thanks Igor! >> >> >> On Fri, Oct 31, 2008 at 2:59 PM, Igor Vaynberg <[EMAIL PROTECTED]>wrote: >> >>> put the container back, override its istransparentresolver() and return >>> true >>> >>> -igor >>> >>> On Fri, Oct 31, 2008 at 2:50 PM, Andrew Berman <[EMAIL PROTECTED]> >>> wrote: >>> > Actually, i had something more like this: >>> > >>> > <body wicket:id="body"> >>> > <form wicket:id="form">...</form> >>> > <wicket:child/> >>> > </body> >>> > >>> > And in the child: >>> > >>> > <form wicket:id="form"></form> >>> > >>> > When I removed the WebMarkupContainer on the body tag, everything >>> worked >>> > perfectly. >>> > >>> > On Fri, Oct 31, 2008 at 2:48 PM, Andrew Berman <[EMAIL PROTECTED]> >>> wrote: >>> > >>> >> I figured out why it was happening. It was because I put a >>> >> WebMarkupContainer on the body tag which includes the wicket:child. >>> So I >>> >> had: >>> >> >>> >> <body wicket:id="body"> >>> >> <wicket:child/> >>> >> </body> >>> >> >>> >> I need to be able to dynamically update the class attribute on the >>> body tag >>> >> which exists in the parent page, how can I do this since the way I >>> want to >>> >> do it doesn't work? >>> >> >>> >> >>> >> On Thu, Oct 30, 2008 at 11:28 PM, Nino Saturnino Martinez Vazquez Wael >>> < >>> >> [EMAIL PROTECTED]> wrote: >>> >> >>> >>> Really strange... I have something similar on 1.4, although never >>> more >>> >>> that 1 nested form. >>> >>> >>> >>> Could you show us some code and markup cut out? >>> >>> >>> >>> >>> >>> Andrew Berman wrote: >>> >>> >>> >>>> Hello, >>> >>>> >>> >>>> I am using Wicket 1.3.5 and I created a panel which contains a form. >>> I >>> >>>> have >>> >>>> a parent template page and a child of the parent page, both of which >>> >>>> contain >>> >>>> an instance of the panel. However, even if I give the panels two >>> >>>> different >>> >>>> ids, I get an error like: >>> >>>> >>> >>>> The component [MarkupContainer [Component id = emailLabel]] has the >>> >>>> same wicket:id as another component already added at the same level >>> >>>> >>> >>>> Why is this happening since I am putting them in a different part of >>> >>>> the hierarchy? >>> >>>> >>> >>>> Thanks, >>> >>>> >>> >>>> Andrew >>> >>>> >>> >>>> >>> >>>> >>> >>> >>> >>> -- >>> >>> -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] >>> >>> >> >
