>>> <div wicket:id="for-admins-only"> >>> <div wicket:id="salary"></div> >>> <!-- a bunch of other components --> >>> </div> >>> >>> now the developer takes the "salary" div and moves it out of the >>> "for-admins-only" div. guess what, your *designer* has just opened a >>> huge security hole in your application. who would use wicket if such >>> things were so easily possible?
Traditional way can be supported, still, where it is needed. Automated regression testing is a good practice ;) Actually this hierarchy-less scheme can be implemented using a helper method: HierarchyUtils.helpMeAddThisComponentToItsParent(panel, component); *** Martin >> >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
