Thanks a lot for the suggestion finally I solved the problem. Anyway I would find more helpful a clear debug that shows visually the internal hierarchy of components. Just to find quicker the bugs Andrea
igor.vaynberg wrote: > > it helps when you paste the stacktrace > > -igor > > > On 8/31/07, andrea pantaleoni <[EMAIL PROTECTED]> wrote: >> >> >> Hi, >> I build a page quite complex with 10 panels several listview a nd other >> components >> When I try to run the application I got always an error: >> hierarchy does not match (markup and page components) >> Anyone knows a way to DEBUG wicket to understand how is built the >> internal >> hierarchy of components for a page? >> >> >> Thanks a lot for any suggestion >> >> -- >> View this message in context: >> http://www.nabble.com/Hierarchy-of-components-tf4360349.html#a12427104 >> Sent from the Wicket - User mailing list archive at Nabble.com. >> > > -- View this message in context: http://www.nabble.com/Hierarchy-of-components-tf4360349.html#a12429312 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
