Dez 10 2009
With the release of GWT 2.0 there are several new features (like Code Splitting, Compiler improvements, faster development mode) introduced and i decided to make a test run on my current enterprise project to see what have changed in this points:
- Compilation time
- API changes
- Startup time of the new Development Mode
- Problems with other libraries
My enterprise project currently needs 66 seconds to build 8 permutations and is using this technologies:
- GWT 1.7.1
- GXT 2.1.0
- GIN 1.0 (with Guice 2.0)
- GWT-Presenter 1.0.0
- GWT-Log 2.6.2
- gwtrpc-spring 1.01
- Spring Framework 2.5.6
- Spring Security 2.0.5
- Hibernate Libs 3.x (core, annotation, validator…)
After i have replaced the old gwt-jar files with the new files, cleaned the project, i started the build target and launched the application. Here are the results:
Without compiler optimization the build need 107 seconds for 8 permutations. Using the draftCompile parameter the build needs “only” 82 seconds. These are not the results i have awaited.
Due to the fact that my build runs through without any errors or warnings, i think the major switch from listener to handler was done with the migration vom GWT 1.5 to 1.6 . So i think there aren’t any critical showstoppers waiting for me.
Startup time of the new Development Mode
Changing from com.google.gwt.dev.HostedMode to com.google.gwt.dev.DevMode was a great speedup! Using any browser you want, instead of this old Hosted Mode-Browser is a useful improvement. I can strongly recommend google Chrome 4 with the new Speed Tracer for development.
Problems with other libraries
In the technology-list above you can see that i use a wide range of gwt-technologies. I had some doubts about GXT, because i am using many widgets from it like the TabPanel, Drag and Drop, special Layouts, TreePanels, Accordion Window, Grids… , but i did not noticed any errors! I launched my Selenium-Tests many times and every result was green. The people from GXT have done a good job with the recently released version 2.1.0 .
Overall i think that migration could be possible with less effort if you have implemented an extensive test-suite. I see the most problems in Widget libraries like GXT, SmartGwt.. which are using listeners from API 1.5 .
If you have any comments, drop a line below.
4 responses so far