I'd still argue that the time of these traditional server-side web frameworks has passed. Static HTML+JavaScript applications (with client-side frameworks like YUI or ExtJS) and server side REST/JSON services (with Jersey or something similar) are the best way to go.
Using 100% pure client HTML/CSS/JS rather than web framework template files (.jsp, .gsp, etc) works way better with tools like DreamWeaver and gives designers maximum independence from server-side programming. Especially given the criteria you list, this is easily a better fit. On Feb 17, 8:38 am, Lenny P <[email protected]> wrote: > So here is a quick summary of what I found out in my lengthy research: > It went down to 5 candidates, JSF, GWT, RIFE, Tapestry & Grails. > I had a couple of must-have criteria: > - A web designer has to be able to read/write the app via DreamWeaver > or other non-programmer tool > - UI has to be built in a definition language, not a programming > language, i.e. no parent.addXXX(child) > - Easy to use, and integrates with the current web projects in use. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
