Eclipse Community Forums: ServerTools (WTP)

Home » Language IDEs » ServerTools (WTP) » Java Build Path Projects

Java Build Path Projects [message #159954]

Thu, 09 February 2006 15:46

Eclipse User

I am stuck, I have a Web Service project that I created from a WSDL file.
I generate the client JSP and run it and I get the expected result back
w/o adding any code.

I want to add a reference in the project to call code within another
project within the same work area. I goto properties->Java Build
Path->Projects, hit the add button, and select the desired project from
the list.

I then goto properties->Project References and check the project that I
want to reference.

I add the code in the project_nameSoapImpl.java file to reference the code
in the other project. It generates the import statement for the code
within the other project, so I know that it is recognizing the other
project.

Then I launch the JSP client and call the same service that I had called
before. The code runs find until it tries to instansiate an instance of
the referenced project class. I then get a exception:
java.lang.NoClassDefFoundError error message, that states that it cannot
find the org/bass/processing/SessionSupportServices. However, it placed
the import statement within the .java file when I added the code (import
org.bass.processing.SessionSupportServices;" and did not produce any
errors.

I am at a loss, it recognizes it when I am editting the code but not when
I run the test.

Also, I had this running before I upgraded to JDK 1.5, Tomact 5.5.15, and
Axis 1_2_1. I am currently running Eclipse 3.1.

I updates these files because I wanted to be able to use the enum that was
included in JDK 1.5. This created a issue with the Axis package names, so
that is why I updated those.

I appreciate any help or insight into this that you can provide.

Thanks,
Ben

Re: Java Build Path Projects [message #159962 is a reply to message #159954]

Thu, 09 February 2006 16:21

Eclipse User

This may help, I am including the contents of the .classpath that exists
at the root of the project. I hope this helps someone understand what is
going on. Please note that the reference to the other projects is
present. I'm not sure what the combineaccessrules="false" means.

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="con"
path=" org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.inte rnal.debug.ui.launcher.StandardVMType/jdk1.5.0_06 "/>
<classpathentry kind="con"
path=" org.eclipse.jst.server.core.container/org.eclipse.jst.server .tomcat.runtimeTarget/C-_Program
Files_Apache Software Foundation_Tomcat 5.5.15"/>
<classpathentry combineaccessrules="false" exported="true" kind="src"
path="/BASS_BOMProcessing"/>
<classpathentry combineaccessrules="false" exported="true" kind="src"
path="/BASS_DatabaseProcessing"/>
<classpathentry combineaccessrules="false" exported="true" kind="src"
path="/BASS_FileProcessing"/>
<classpathentry combineaccessrules="false" exported="true" kind="src"
path="/BASS_Processing"/>
<classpathentry
output=".deployables/BASS_WebServices_5.5.15/WEB-INF/classes " kind="src"
path="JavaSource"/>
<classpathentry kind="con"
path=" org.eclipse.jst.j2ee.internal.web.container/BASS_WebServices _5.5.15 "/>
<classpathentry kind="output" path="bin"/>
</classpath>

Thanks,
Ben

Re: Java Build Path Projects [message #159980 is a reply to message #159962]

Thu, 09 February 2006 16:39

Eclipse User

Additional information that may help. I was comparing the .wtpmodules
files between the old version that successfully referenced the external
projects and the newer version that does not and I found some significant
differences. I will attach the new .wtpmodules files first.

You should notice that on this file there are no <dependent-module/>
entries. I think this is probably my issue, I just don't know how to fix
it or why it isn't generating. I will include the old .wtpmodules file
entires beloew the new entires. Notice that it has the references to the
<dependent-module/>

Thanks for any help,
Ben

NEW wtpmodules file:
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId">
<wb-module deploy-name="BASS_WebServices_5.5.15">
<module-type module-type-id="jst.web">
<version>2.4</version>
<property name="context-root" value="BASS_WebServices_5.5.15"/>
<property name="java-output-path" value="/bin/"/>
</module-type>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/JavaSource"/>
<wb-resource deploy-path="/" source-path="/WebContent"/>
</wb-module>
</project-modules>

OLD .wtpmodules file:
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId">
<wb-module deploy-name="BASS_WebServicesMod">
<module-type module-type-id="jst.web">
<version>2.4</version>
<property name="context-root" value="BASS_WebServicesMod"/>
</module-type>
<wb-resource source-path="/BASS_WebServicesMod/JavaSource"
deploy-path="/WEB-INF/classes"/>
<wb-resource source-path="/BASS_WebServicesMod/WebContent"
deploy-path="/"/>
<dependent-module deploy-path="/WEB-INF/lib"
handle="module:/resource/BASS_BOMProcessing/BASS_BOMProcessing ">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module deploy-path="/WEB-INF/lib"
handle=" module:/resource/BASS_DatabaseProcessing/BASS_DatabaseProces sing ">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module deploy-path="/WEB-INF/lib"
handle="module:/resource/BASS_FileProcessing/BASS_FileProcessing ">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module deploy-path="/WEB-INF/lib"
handle="module:/resource/BASS_Processing/BASS_Processing">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>

Re: Java Build Path Projects [message #159997 is a reply to message #159980]

Thu, 09 February 2006 16:56

Eclipse User

you need to add the dependent projects to the J2EE dependencies in the
properties page. be sure that your dependent projects do not have any
spaces in their names otherwise the classpath will get screwed up and
you will end up with an Rmi unmarshalling exception of all things.

i also had problems with the dependent project libraries not being found
, ClassNotFound exception, and had to copy its libraries to the web
service project.

hope this helps, Mitchell

Ben Sisson wrote:
> Additional information that may help. I was comparing the .wtpmodules
> files between the old version that successfully referenced the external
> projects and the newer version that does not and I found some
> significant differences. I will attach the new .wtpmodules files first.
>
> You should notice that on this file there are no <dependent-module/>
> entries. I think this is probably my issue, I just don't know how to
> fix it or why it isn't generating. I will include the old .wtpmodules
> file entires beloew the new entires. Notice that it has the references
> to the <dependent-module/>
>
> Thanks for any help,
> Ben
>
> NEW wtpmodules file:
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId">
> <wb-module deploy-name="BASS_WebServices_5.5.15">
> <module-type module-type-id="jst.web">
> <version>2.4</version>
> <property name="context-root" value="BASS_WebServices_5.5.15"/>
> <property name="java-output-path" value="/bin/"/>
> </module-type>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/JavaSource"/>
> <wb-resource deploy-path="/" source-path="/WebContent"/>
> </wb-module>
> </project-modules>
>
> OLD .wtpmodules file:
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId">
> <wb-module deploy-name="BASS_WebServicesMod">
> <module-type module-type-id="jst.web">
> <version>2.4</version>
> <property name="context-root" value="BASS_WebServicesMod"/>
> </module-type>
> <wb-resource source-path="/BASS_WebServicesMod/JavaSource"
> deploy-path="/WEB-INF/classes"/>
> <wb-resource source-path="/BASS_WebServicesMod/WebContent"
> deploy-path="/"/>
> <dependent-module deploy-path="/WEB-INF/lib"
> handle="module:/resource/BASS_BOMProcessing/BASS_BOMProcessing ">
> <dependency-type>uses</dependency-type>
> </dependent-module>
> <dependent-module deploy-path="/WEB-INF/lib"
> handle=" module:/resource/BASS_DatabaseProcessing/BASS_DatabaseProces sing ">
> <dependency-type>uses</dependency-type>
> </dependent-module>
> <dependent-module deploy-path="/WEB-INF/lib"
> handle="module:/resource/BASS_FileProcessing/BASS_FileProcessing ">
> <dependency-type>uses</dependency-type>
> </dependent-module>
> <dependent-module deploy-path="/WEB-INF/lib"
> handle="module:/resource/BASS_Processing/BASS_Processing">
> <dependency-type>uses</dependency-type>
> </dependent-module>
> </wb-module>
> </project-modules>
>
>
>

Re: Java Build Path Projects [message #160019 is a reply to message #159997]

Thu, 09 February 2006 21:19

Eclipse User

Mitchell,

This seems to be exactly what I am looking for but I cannot find the J2EE
Dependency page. I've looked up the the views as well as the
perspectives. I have also checked the properties of my project and the
Preferences and cannot find any reference to a dependency page. I checked
the Eclipse help and it has a great view of a dependency page, and looks
like exactly what I need. However, the help does not explain how to get
the dependency page open. This may seem silly but can you please explain
to me where the dependency page comes from and how to open it up.

Thanks for you input and guidance,
Ben

Re: Java Build Path Projects [message #160178 is a reply to message #160019]

Fri, 10 February 2006 12:40

Eclipse User

Ben, the dependency page is found on the project properties, right above
the build path i think. if it is not there it could be that your
project is not of the correct type or that your WTP installation has a
problem. try creating a new web services project and see if it has the
page.

Mitchell

Ben Sisson wrote:
> Mitchell,
>
> This seems to be exactly what I am looking for but I cannot find the
> J2EE Dependency page. I've looked up the the views as well as the
> perspectives. I have also checked the properties of my project and the
> Preferences and cannot find any reference to a dependency page. I
> checked the Eclipse help and it has a great view of a dependency page,
> and looks like exactly what I need. However, the help does not explain
> how to get the dependency page open. This may seem silly but can you
> please explain to me where the dependency page comes from and how to
> open it up.
>
> Thanks for you input and guidance,
> Ben
>

Re: Java Build Path Projects [message #160201 is a reply to message #160178]

Fri, 10 February 2006 13:10

Eclipse User

I'm in the J2EE perspective looking at my project. I right click on the
project and select properties. The list includes:
Info
BeanInfo Path
Builders
EAR modules
Java Build Path
Java Code Style
Java Compiler
Javadoc Location
Java JAR Dependencies
Project References
Server
Task Tags
Validation
WS-I Compliance

My project is a Web Service project generated from a WSDL file.

I am running Eclipse 3.1, JDK 1.5, Tomcat 5.5.15, and Axis 1_2_1.

I have WTP 0.7 installed in Eclipse. I would like to install WTP 1.0 but
haven't figure out how to install it w/o rebuilding the entire Eclipse
project.

Thanks,
Ben

Re: Java Build Path Projects [message #160587 is a reply to message #160201]

Mon, 13 February 2006 11:20

Eclipse User

There was an issue with my version of Eclipse that I was running. I can't
explain but once I created a new version of of Eclipse:
Eclipse 3.1.1 with WTP 1.0 (all in one download and extract) I had no
problems.

Thanks for the support and help provided by everyone,
Ben

Previous Topic:	Web tools bug 104993
Next Topic:	WTP & log4j

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Mar 20 15:32:16 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter