Hi there, I'm not really sure if searching a component by its ID is a good idea - It kinda' breaks modularity and goes against the OO approach.
I have never searched a component by its ID but assuming you need the full path (hierarchy) to it, such component will be hard to use in any other context because you harcoded the path to that component. Whenever I need to get access to a component I simply store it in a Map or component List for later search and/or use. Best regards nuno -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Is-there-a-way-to-search-component-by-its-wicket-ID-tp4651175p4651221.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
