My solution is to compile the GWT module first and then move GWT SDK -
GWT2.1.0 after Apache Tomcat and Web App Libraries library. The
dynamic web project will then build itself. Restart Tomcat ,
everything works.
I am not sure if this is a good solution. Every time I check out a new
project, I
you might think about moving the GWT client code (which contains
client and shared packages) into custom project to not mixup
classpaths during compile and runtime, after all GWT produces piece of
JS which is actually the one your project needs. so you dont need to
recompile everytime, rather
Thanks for the response ep. I was thinking about that as well.
I also read another guy's post. He put GWT in seperate project. So two
projects, one for front end, one for back end.
It will be ideal whenever eclipse rebuilds the project, it compiles GWT as
well. Or GWT stop override tomcat libary
I also read another guy's post. He put GWT in seperate project. So two
projects, one for front end, one for back end.
it is indeed very common to do it this way, maven could also help you
here
It will be ideal whenever eclipse rebuilds the project, it compiles GWT as
you can do so, by
I am using eclipse(Galileo)+tomcat plugin+gwt plugin.
The project uses Spring MVC+ lots of JSP, only one part of the system
using GWT. That is for menu items.
At the moment, every single time I check out a project, I have to
compile the GWT module before I start my tomcat.
There is known problem
More details:
I am using eclipse(Galileo)+tomcat plugin+gwt plugin, The java build
libraries’ order: JRE System libary
GWT SDK - GWT2.1.0
Apache Tomcat
Web App Libraries
The project uses Spring MVC+ lots of JSP, only one part of the system using
GWT. That is for menu items.
At the moment, every
