Negative experience with GWT
Nowadays, it is considered bad form to develop web applications without using AJAX. So I decided to keep up with the whole world and keep up with web 2.0 technologies. Having studied the topic a bit on the subject of what is AJAX, I decided to focus on the GWT framework. The idea of GWT is tempting enough for a java developer since allows you to create AJAX applications without knowing javascript. All code is written in java, which is later compiled into javascript sources.
After reading the documentation for some time, I realized that a GWT application is one main component that contains other components (interface elements). The main component is the entry point to the GWT application. All requests from interface elements pass through the controller of the main component.
After practicing with the API and more or less comfortable, I decided to screw Spring to GWT. Unfortunately, using the Spring plus GWT bundle on the fly will fail. The reason is that all requests go through a special GWT servlet. Having evaluated the situation, I realized that making friends with Spring and GWT requires additional time for research and implementation, which of course did not please me because this is already a kind of shamanism. But I did not want to abandon Spring, so I climbed into google in the hope of finding ready-made implementations. As it turned out, everything is not so bad. There are enough solutions on the network for this task (http://code.google.com/p/gwtrpc-spring, technophiliac.wordpress.com/2008/08/24/giving-gwt-a-spring-in-its ... )
Building a project on GWT is not complicated. There are ant scripts for this. Personally, I stopped using ant for building projects long ago. Maven is much more convenient for these purposes. Having made a simple search query in google, I found a project supporting the assembly of a maven project on GWT (http://code.google.com/p/gwt-maven).
The next step was to integrate Acegi Security (Spring Security). This task is also not so simple. I could not find any acceptable solution (it may appear in the future). Therefore, I decided to configure security using the standard means of a web container.
After working with GWT for a total of about a month and a half and learning more deeply the nuances of development for GWT, I decided - this framework does not suit me. As a result of my research, we can conclude:
GWT integrates heavily with other products (Spring, Acegi). Integration is difficult to accomplish without breaking the standard development cycle for GWT, which may lead to incompatibility with future versions of GWT (you need to consider this). Debugging a GWT application is done through the GWT console. Debugging in the GWT console is a common log analysis. That is, you have to forget about all the power of the debugger development environment. Another drawback is that the GWT application will not be indexed by search engines since GWT is javascript, which, as you know, is not parsed by search engine indexing works.
After reading the documentation for some time, I realized that a GWT application is one main component that contains other components (interface elements). The main component is the entry point to the GWT application. All requests from interface elements pass through the controller of the main component.
After practicing with the API and more or less comfortable, I decided to screw Spring to GWT. Unfortunately, using the Spring plus GWT bundle on the fly will fail. The reason is that all requests go through a special GWT servlet. Having evaluated the situation, I realized that making friends with Spring and GWT requires additional time for research and implementation, which of course did not please me because this is already a kind of shamanism. But I did not want to abandon Spring, so I climbed into google in the hope of finding ready-made implementations. As it turned out, everything is not so bad. There are enough solutions on the network for this task (http://code.google.com/p/gwtrpc-spring, technophiliac.wordpress.com/2008/08/24/giving-gwt-a-spring-in-its ... )
Building a project on GWT is not complicated. There are ant scripts for this. Personally, I stopped using ant for building projects long ago. Maven is much more convenient for these purposes. Having made a simple search query in google, I found a project supporting the assembly of a maven project on GWT (http://code.google.com/p/gwt-maven).
The next step was to integrate Acegi Security (Spring Security). This task is also not so simple. I could not find any acceptable solution (it may appear in the future). Therefore, I decided to configure security using the standard means of a web container.
After working with GWT for a total of about a month and a half and learning more deeply the nuances of development for GWT, I decided - this framework does not suit me. As a result of my research, we can conclude:
GWT integrates heavily with other products (Spring, Acegi). Integration is difficult to accomplish without breaking the standard development cycle for GWT, which may lead to incompatibility with future versions of GWT (you need to consider this). Debugging a GWT application is done through the GWT console. Debugging in the GWT console is a common log analysis. That is, you have to forget about all the power of the debugger development environment. Another drawback is that the GWT application will not be indexed by search engines since GWT is javascript, which, as you know, is not parsed by search engine indexing works.