|
|
Re: java.lang.NoClassDefFoundError [message #172398 is a reply to message #159859] |
Mon, 26 June 2006 09:35 |
Eclipse User |
|
|
|
Originally posted by: pbarry.prosys.fr
I got exactly the same problem.
I think I can bypass it by creating a .jar from the referenced project and
put it in the lib directory of my web project, but that would be slightly
heavier to develop, if I want to modify my referenced project often.
Still, if you found the solution since, I'd greatly apreciate it
Regards,
Paul Barry Delongchamps.
"Ben Sisson" <bsisson@simventions.com> a
|
|
|
Re: java.lang.NoClassDefFoundError [message #172787 is a reply to message #172398] |
Fri, 30 June 2006 13:31 |
Chuck Bridgham Messages: 35 Registered: July 2009 |
Member |
|
|
Paul Barry Delongchamps wrote:
> I got exactly the same problem.
> I think I can bypass it by creating a .jar from the referenced project and
> put it in the lib directory of my web project, but that would be slightly
> heavier to develop, if I want to modify my referenced project often.
> Still, if you found the solution since, I'd greatly apreciate it
> Regards,
> Paul Barry Delongchamps.
> "Ben Sisson" <bsisson@simventions.com> a écrit dans le message de news:
> 900b59d34767eb2c3c7b08e9308728bd$1@www.eclipse.org...
>>I was comparing my old project that I created with Eclipse 3.1, Tomcat
>>5.0.23, SDK 1.4, and Axis 1_1 with the new project created with Eclipse
>>3.1, Tomcat 5.5.15, JDK 1.5, and Axis 1_2_1. I compared the .deployables
>>folders in both projects and found some differences that I cannot explain.
>>
>> The WEB-INFlib folder for the older project contained the jar files for
>> the referenced projects. However, the WEB-INFlib folder for the new
>> project does not contain the jar files for the referenced projects.
>> I cannot explain the differences. I compared the project properties of
>> the old and new projects and they are setup almost identically. The only
>> differences beeing that versions of JDK and Axis that are referenced.
>> Both projects have the same reference projects selected in the Java Build
>> Path->Projects tab. The Order and Export are the exact same.
>>...
It sounds like you have been working with R0.7 workspaces that contained
the ".deployables" folder. And possibly have upgraded to R1.0?
The .deployables folder was used to "assemble" the referenced
projects/libraries under a single folder root, and we pointed the server
adapter to this location. In R1.0, we abandoned this idea of constantly
"copying" the relevant files, but still rely on the dependencies created
with the "J2EE Module Dependencies" property sheet.
I recommend moving up to the callisto release today, as there are many
options for setting up project/archive dependencies. The classpath entries
are added to you project, and in the case of tomcat, are assembled in the
proper directory at publish time.
Thanks - Chuck
|
|
|
Powered by
FUDForum. Page generated in 0.02278 seconds