1) Mac Pro Leopard , 8G RAM, QUAD Core chips
2) Eclipse 3.2
3) Eclipse web tools, managing/running tomcat via the embedded mode (not external to eclipse)
Ive found that, over time, I now have to restart the server for even the slightest changes, and
sometimes I have to restart the server, build project, publish, clean, etc... multiple times to get things working....
This problem is especially bad if I change the value of a static variable, for example.
Please provide me with some advise on this issue. In particular -
1) what is the difference between publish and clean ?
2) what is the best simple way to now that everything is synchronized ?
3) what is the meaning of the stack trace that tomcat is showing me (above) ?
4) any other comments/help would be appreciated .
Is glassfish a better alternative (i.e. is it more intuitive or stable for management of complex projects )?
One minor detail, my Eclipse web environment includes 5 projects, all of which are large, and there are cross cutting dependencies between the projects. For example, one is a general utilities project.
Im just adding this in so that, in case large source dependencies slow down or interfere with tomcat dependencies ,that may be a hypothetical reason for the inefficiency im experiencing.
Hi Guys : This problem is definetly systemic. There are various classes where, if I introduce any runtime exception, the server
simply spits out that nebulous stack trace shown above. This is causing tremendous difficulties in development !
ODDLY .... If I add System.out.println statements to random areas in the jsp page which is causing the exception, I get
more meaningful stack traces from tomcat.