I told when a jsp file is edited on Eclipse WTP, and published, the
tomcat work directory is removed and regenerated.
I checked more and more and finally found out that this happens only
when the project web context root is "/" in Eclipse Project properties.
When a project has other context root (except "/"), this
phenomenon(removing tomcat work directory) does not happen.
Thanks,
KwonNam.
2011년 01월 21일 15:27, Son KwonNam 쓴 글:
I checked the timestamp of JSP and class/java file.
When I edited JSP in Eclipse editor and saved the file, it was published
to
workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/myweb/...
directory.
I checked the contends and times stamp of jsp file, it was proper.
Also checked
workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/work/Catalina/localhost/_/org/apache/jsp/...
The class and java file was properly generated and compiled after the
jsp is published.
The thing I found strange is, when a jsp is published to
wtpwebapps/myweb/... directory, the counterpart class directory is
removed and remade, then java source is generated and compiled.
Actually when I checked deeply, not just jsp counterpart class
directory, the root class
directory(workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/work/Catalina/localhost/_)
is removed when a jsp is edited and published then if I request the JSP
on a web browser, the class directory and java/class files are regenerated.
I use Tomcat 6.0.30.
Our whole team members suffer from this problem.
We use JDK 6. Most of us use Windows 7 64Bit, but I use Ubuntu 10.10
32bit. So I think it's not a problem of OS.
And most of the jsp files are under WEB-INF/jsp directories. But this
problem happens to JSP files not under WEB-INF directory.
Thanks.
2011년 01월 20일 02:21, Mark Thomas 쓴 글:
On 19/01/2011 16:04, KwonNam Son wrote:
I'm developing an web application on Eclipse Helios, WTP, Tomcat
6.0.29(and just upgraded to 6.0.30).
I suffer from ClassNotFoundException a lot of times on both 6.0.29/30.
It's not about usual classes or jar. It's about JSP generated java
class.
For example, when I request /jsps/test.jsp, the stack trace looks like
the following.
java.lang.ClassNotFoundException:
org.apache.jsp.jsps.test_blahblah.class
But org.apache.jsp.jspa.test_blahblah.class surely exists in the work
directory.
When this happens, I just shutdown the tomcat on eclipse and start it
again. That's all. Then the jsp works fine. But after a few minutes it
happens again.
What's the problem??
An integration issue in WTP maybe? I've never really got to the bottom
of exactly how that plug-in worked. Copying across the new JSP - or just
editing it directly should work.
Next time it happens check the timestamps on the JSP and the class file.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
