> To address this, I wrote some code that gets the component tree, and > either returns a List, or a string with the components' id's and > classes. It can be found at http://gist.github.com/144041. > > Is this useful to anyone? Is there a better way for me to view the > component tree at runtime/test time?
WicketTester has #debugComponentTrees() which seems to do most of what you want, or you can use WicketTesterHelper#getComponentData(). Do they cover the same needs as your code? - Tor Iver --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
