Hi all, I'm raising this question before starting to spend any time on a wicket/facelets proof of concept.
Do we want to go the road of component based web frameworks or not? Please do speak up frankly. Going component based means a wholly different way of thinking about the web page, session handling and so on. Means that the page is not thought as a set of tags anymore, but as a tree of components much like a Swing or SWT user interface. Means that you don't think anymore about forms and post/get request but do receive events from the component on the page. It means that we can get basic/advanced AJAX capabilities almost for free (see icefaces and wicket). It also means that, choosing the appropriate framework, we can get rid of jsp and their compilation, as well as the ugly ability to mix code into the UI description layer (plain JSF still use jsps, but facelets has a different view handler and does parse xhtml pages as xml, does not compile them). Sure this is compelling for me, since I'm mostly a Swing developer and the only web framework I ever used is ASP.NET, (different language but same approach, component based too). What about you? Cheers Andrea ------------------------------------------------------------------------- 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 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
