On Fri, Nov 5, 2010 at 10:07 AM, Martin Makundi < martin.maku...@koodaripalvelut.com> wrote:
> > I know that in this case (Jeremy wrote that) you must provide > > uniqueness of components in whole page but it also can be resolved > somehow > > +1 > > Also DOM requires id uniqueness according to spec so it is nothing new > to web developers. > Martin, Did you understand what Jeremy and Michal described above ? If you have to use libraries A and B that provide Wicket components and both of them use "message" or "feedback" as component id in any of their components then how your application will deal with that ? > > ** > Martin > > > > >> I think if you find component hierarchies to be "hell", you probably > >> aren't > >> using Wicket right. Break things down into small reusable chunks using > >> Panels and you will find everything gets much, much easier. > > > > --------------------------------------------------------------------- > > 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 > >
