I don't know if it's a good idea, building a 100% GWT monolithic application but I reach the compiler bounds with a medium application (400 java sources in client directory and some gwt modules). It's possible to increase java memory or factorize some java code parts, but it's not a solution. Soon you reach another error with the message: [ERROR] Unexpected internal compiler error java.lang.StackOverflowError: null If this is not only a memory issue considering the growing size of generated java script application page. Furthermore running in host mode become longer when your app is growing.
I am sure in GWT framework team, you have done a very good job. I don't want to misuse it ! What is a good strategy if I want such application ? An idea I try is to split the application but I need an extra Html page to embed all parts. This page is a pure html page or an another gwt application. But I need to extract some shared parts as libraries and to implement an extra mechanism to share context information between parts. Then I notice that the historic management doesnt fit... I also imagine to extract some java code as a separated javascript but I choose GWT to avoid dealing with JS and appreciate the Eclipse dev cycle, with debug... and java is realy cool. Not so easy ! If someone have a good idea to share... ? Gilles. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
