Google Web Toolkit -- adapting pains and issues
I have been first exposed to GWT on November 2006 and in one of our Java User group meeting. At that time we are looking to replace our ancient applet based web application. I saw the similarities on how GWT is similar to Java Swing in some of its components. Surely enough our group adapted and went with GWT. Here are the major issues that we have encountered. The issues are based on some wrong assumptions about GWT. Here is some points that our team missed about GWT. - GWT is JavaScript - JavaScript is executed in the clients Browser - GWT is not a web application framework - Be Aware of GWT Security issues GWT is JavaScript Even though GWT is coded using Java and leverages Java Tools, at the end of the day it is still JavaScript. So it is subjected to JavaScript issues like the following: - Threading - JavaScript is event driven and has single threaded model for development. So codes that are executed will be solely based on events. - Code size - even though there is no limit on how