Dynamic web project can't find its own classes after CVS checkout [message #194360] |
Tue, 12 June 2007 22:50  |
Eclipse User |
|
|
|
Hi again.
Using the following...
Eclipse: 3.3.RC2
WTP-5-2.0RC2
Tomcat 6.0.13
JDK 1.5.12
....I have a situation where my dynamic web project runs great on the
machine I set it up on, but when shared and checked out by others, it
fails. When checked out into a new project, I'm able to launch it
within a tomcat server using "Run As > Run on Server". The server
starts up, but throws a number of exceptions when loading the page,
indicating that it can't find the project's own compiled classes, e.g.:
org.apache.jasper.JasperException: /index.jsp(21,0) The value for the
useBean class attribute com.kteh.web.servlets.WhatsOnBean is invalid.
This indicates to me that it can't find the class
com.kteh.web.servlets.WhatsOnBean, yet the corresponding java file
exists within the project under /src. I then get:
java.lang.ClassNotFoundException: org.apache.jsp.index_jsp
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
etc.
.... indicating that tomcat can't find the JSP-derived class for the request!
I've been able to reproduce this on a number of machines, all with
identical configurations (as described above), which are also the same
as the original machine on which the project was created (and works fine).
Any help is greatly appreciated.
Ken
|
|
|
|
Re: Dynamic web project can't find its own classes after CVS checkout [message #194507 is a reply to message #194372] |
Wed, 13 June 2007 20:36   |
Eclipse User |
|
|
|
Hi-
Yes it would seem like there is missing metadata, but that was all being
checked in.
To make sure I wasn't missing anything obvious I rebuilt my project from
scratch, and again it ran beautifully on my own machine. However,
again, when sharing the project, then checking it out on a new machine,
it failed in strange ways. For one, it did not maintain j2ee project
dependencies, despite the fact that the projects have identical names.
Furthermore, the classes in /src where not being compiled to
build/classes: even when forcing a clean build, /build/classes remains
empty, despite the fact that it's still configured as the output dir in
project prefs > java build path > source.
I'm fresh out of ideas at this point...
Thanks for any help,
Ken
Konstantin Komissarchik wrote:
> My guess is that you are not putting your project metadata into CVS so
> when the project is synced to a different machine, Eclipse and WTP don't
> know quite what to do with it. Make sure that for instance .project,
> .classpath, and all of the contents of the .settings directory are in CVS.
>
> - Konstantin
My original post:
Hi again.
Using the following...
Eclipse: 3.3.RC2
WTP-5-2.0RC2
Tomcat 6.0.13
JDK 1.5.12
....I have a situation where my dynamic web project runs great on the
machine I set it up on, but when shared and checked out by others, it
fails. When checked out into a new project, I'm able to launch it
within a tomcat server using "Run As > Run on Server". The server
starts up, but throws a number of exceptions when loading the page,
indicating that it can't find the project's own compiled classes, e.g.:
org.apache.jasper.JasperException: /index.jsp(21,0) The value for the
useBean class attribute com.kteh.web.servlets.WhatsOnBean is invalid.
This indicates to me that it can't find the class
com.kteh.web.servlets.WhatsOnBean, yet the corresponding java file
exists within the project under /src. I then get:
java.lang.ClassNotFoundException: org.apache.jsp.index_jsp
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
etc.
.... indicating that tomcat can't find the JSP-derived class for the request!
I've been able to reproduce this on a number of machines, all with
identical configurations (as described above), which are also the same
as the original machine on which the project was created (and works fine).
Any help is greatly appreciated.
Ken
|
|
|
Re: Dynamic web project can't find its own classes after CVS checkout [message #194515 is a reply to message #194507] |
Fri, 15 June 2007 14:40  |
Eclipse User |
|
|
|
Originally posted by: kosta.bea.com
A good place to start figuring out what's going wrong is to compare the
project metadata from the original machine to what you are getting on
the other machine. Pay particular attention to the files that start with
'.' in the project root (such as .project and .classpath) as well as the
contents of the .settings directory.
- Konstantin
|
|
|
Powered by
FUDForum. Page generated in 0.03823 seconds