Martijn Dashorst wrote: > The API will change constantly, but not dramatically. i.e. I seriously > doubt that *all* components will have to change again. But some minor > things are bound to change. > I hope the changes will be mostly compatible, if not fully. API changes is what drove me away from Tapestry. The change from version 3 to 4 was so big that it is simply easier to learn and use wicket.
Can't wicket use the approach followed by SUN which is never to change an interface in a downward incompatible way but instead to add new APIs and make old ones deprecated or extend them? I believe SUN would have been completely out of business by now if they would have changed fundamental Java APIs. ------------------------------------------------------------------------- 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-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
