> wicket component hierarchy is dynamic, so there is no predicting it at > compile time. this is one of the most powerful features of wicket.
Yes but each component is always fixed relative to its parent. The html markup fixes the hierarcy, so something might be devised here. > What about introducing an xpath-ish like expression API that could > help you search for components within the hierarchy? I am not familiar with this but sounds good, anybody have a suitable example for this? ** Martin > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
