- GWT is a Java-to-Javascript compiler. It will take Java source code and compile it to JavaScript that runs in the browser. Being a compiler, it knows everything that there is to know about your program, so it's able to optimise your code (as well as its own code) in much the same way that a C compiler optimises C programs. The end result is that there is no javascript library for your users to download. There's only your application, and your users will only download as much javascript as your application actually uses. You can even defer binding so that modules are loaded only when needed.
For example, jQuery is about 3400 lines of JavaScript code, and compresses to about 15kB. The equivalent Java code compiles to 720 bytes with Google Web Toolkit.
- Everything depends on your application. I don't have experience with Wicket, not much with JSF. I have big experience with GWT.
GWT is good if your application has to be mostly dynamic. In GWT you can change everything on the page not even calling the server. GWT is compiled to Javascript. On the other hand, if you have big project, it is quite frustrating if your application in development starts few minutes, because it has a lot of code to compile to Javascript. My opinion: it is not good for big projects.
If you don't need to change your pages so much client-side, I would use JSF2 (or Wicket, if I knew it).
ผู้ติดตามบล็อก : 3 คน [
