On Fri, Nov 5, 2010 at 10:16 AM, Martin Makundi < martin.maku...@koodaripalvelut.com> wrote:
> Hi! > > > 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 ? > > You make decision: feedback is either private (traditional) or > protected/panel-scope member. Both ways can be supported. Ifcourse > even better if we can have compile-time conflict resolution (Project > Lombok, Bindgen). > Let's say both libraries are "modern" (because private scope is old-fashion, right) and export "message" with Page scope. Then project X (Lombok, Bindgen) finds the problem at compile time and explain you that both lib A and B export component with the same id. What would you do now ? Throw away either lib A or B and re-write it ? > > ** > Martin > > > > >> > >> ** > >> 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 > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
