> I don't 'get' what someone will possibly understand better from having > getRequestCycle() everywhere in the Java class. If it is a problem of > understanding, then we need some serious extra documentation. > > And while you're at it, why not remove getRequestCycle() and > getSession() also? RequestCycle.get() and Session.get() are just one > extra character, and communicate intent even better?
Exactly! That's the whole point. Less ways to achieve the same thing means less confusion, a smaller API and less interdependencies of that API, making changes in the future easier for us. Simple as that. Eelco ------------------------------------------------------------------------- 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
