maybe wicket 2.0 can refactor the components hierarchy to use the bridge pattern?
for example, i want a Calendar component that will be implemented with jscalendar, yui calendar etc. making Calendar abstract and extending it with YuiCalendar is not efficient if there are other implementations using Yui, since there is probably a lot of code they share. of course i can add the bridge pattern my self, but it will be easier if wicket already has that, since then all the wicket technical stuff is taken care of, and the only thing required is understanding the library i want to integrate with. thanx, ittay -- =================================== Ittay Dror, Chief architect, openQRM TL, R&D, Qlusters Inc. [EMAIL PROTECTED] +972-3-6081994 Fax: +972-3-6081841 http://www.openQRM.org - Keeps your Data-Center Up and Running Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
