Negative GWT Experience
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. After a bit of research on the topic of what AJAX is, I decided to stop my attention on the GWT framework. The idea of ​​GWT is tempting enough for a java-developer because 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 the interface elements pass through the main component controller.
Having practiced with API and more or less accustomed, I decided to fasten Spring to GWT. Unfortunately, using the Spring bundle plus GWT will not work right away. The reason is that all requests go through a special GWT servlet. Assessing the situation, I realized that it would take additional time to research and implement Spring and GWT to make friends, which of course did not make me happy. this is a kind of shamanism. But I didn’t want to give up Spring, so I went to google in the hope of finding ready implementations. As it turned out, everything is not so bad. The network has enough solutions for this problem (http://code.google.com/p/gwtrpc-spring, technophiliac.wordpress.com/2008/08/24/giving-gwt-a-spring-in-its ... ).
Build a project on GWT is not complicated. For this there are ant-skrpty. Personally, I have long ceased to use ant to build projects. Maven is much more convenient for this purpose. Having made a simple search query in google, I found a project that supports building 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 did not manage to find any acceptable solution (perhaps in the future to appear). Therefore, I decided to configure security using standard web container tools.
Having worked with GWT in total for about a month and a half and having learned more deeply the nuances of development for GWT, I made a decision - this framework does not suit me. As a result of my research, we can conclude:
GWT is heavily integrated with other products (Spring, Acegi). Integration is difficult to accomplish without disrupting the standard GWT development cycle, which may lead to incompatibility with future versions of GWT (you need to take this into account). Debugging the GWT application is done via the GWT console. Debugging in the GWT console is a common log analysis. That is, you will have to forget about the full power of the development environment debugger. Another disadvantage is that the GWT application will not be indexed by search engines. GWT is javascript, which, as you know, is not parsed by the 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 the interface elements pass through the main component controller.
Having practiced with API and more or less accustomed, I decided to fasten Spring to GWT. Unfortunately, using the Spring bundle plus GWT will not work right away. The reason is that all requests go through a special GWT servlet. Assessing the situation, I realized that it would take additional time to research and implement Spring and GWT to make friends, which of course did not make me happy. this is a kind of shamanism. But I didn’t want to give up Spring, so I went to google in the hope of finding ready implementations. As it turned out, everything is not so bad. The network has enough solutions for this problem (http://code.google.com/p/gwtrpc-spring, technophiliac.wordpress.com/2008/08/24/giving-gwt-a-spring-in-its ... ).
Build a project on GWT is not complicated. For this there are ant-skrpty. Personally, I have long ceased to use ant to build projects. Maven is much more convenient for this purpose. Having made a simple search query in google, I found a project that supports building 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 did not manage to find any acceptable solution (perhaps in the future to appear). Therefore, I decided to configure security using standard web container tools.
Having worked with GWT in total for about a month and a half and having learned more deeply the nuances of development for GWT, I made a decision - this framework does not suit me. As a result of my research, we can conclude:
GWT is heavily integrated with other products (Spring, Acegi). Integration is difficult to accomplish without disrupting the standard GWT development cycle, which may lead to incompatibility with future versions of GWT (you need to take this into account). Debugging the GWT application is done via the GWT console. Debugging in the GWT console is a common log analysis. That is, you will have to forget about the full power of the development environment debugger. Another disadvantage is that the GWT application will not be indexed by search engines. GWT is javascript, which, as you know, is not parsed by the search engine indexing works.
')
Source: https://habr.com/ru/post/70492/
All Articles