On Thu, 28 Feb 2008, Sven Schliesing wrote: > This works quite good. But I'm having problems with using too much > "internal knowledge" (e.g. the tabs-container id) of the AjaxTabbedPanel. > > Sure, this is more an academically problem. But I'd like to know if
It's not plain academic, because this issue makes your tests more fragile. From early 1.3 through the beta versions and now to 1.3.1, our tests have been breaking up sometimes, for example for issues like that. It can also happen with your own code when its component hierarchy changes. > there's a better approach. Yes, you can use Component.visitChildren(Class, IVisitor) to operate on the wanted component on the hierarchy. jdave-wicket has this built-in (ComponentSpecification.selectFirst() and .selectAll()) and even the cool feature of being able to find the component with a Hamcrest matcher matching on its model object. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
