As I understand it, Echo2 operates on the server side, rather than GWT's approach of translating to client-side JavaScript at compile-time. Therefore your Echo2 Java code is not limited to a translatable subset of Java, but on the downside it generates a lot of chatter between the client and server. Not necessarily a bad thing, but it depends on your needs. I wouldn';t really say it's a "better alternative" across the board.
Fred
On 8/31/07, Rakesh Vidyadharan < rakesh
rakeshv.org">rakesh
rakeshv.org> wrote:
Echo2 is a better alternative for Java developers, since you are not
restricted to just using a subset for Java for the front-end. You
can develop the web front end in much the same fashion as you would a
Swing application (that includes reflection, auto binding etc).
.