[diaxwm]

Hi,

SysConfig: Eclipse 2.1.0, JDK 1.4.1, MyEclipse 2.6.0 running on Windows NT 4.0, JBoss 2.4

I have the following projects:

CORE: Simple Java-project providing base-classes for all apps
GROUP: Simple Java-project providing the ejb-interfaces and valueobjects for this app
WEB: A Web-project providing the user-interface
EJB: AN EJB-project providing the ejb-implementations

EJB depends on GROUP, CORE and some external jars
Web depends on GROUP, CORE and some external jars
GROUP depends on CORE

I have set up these dependencies in the project poperties fpor build-path and also checked “export” for the libs and the projects on which the ejb depends on.

The problem is, that only the contents of the WEB and EJB-project is really inserted in the ear file (btw. in the contained jar/war-files). Neither the external libraries (like struts or log4j) nor the contents of the projects CORE and GROUP are included. 😥

So the deployment is not possible due to ClassNotFoundExceptions. ❗

What am i doing wrong? Do I have to specifiy the exported jars at an additional place? If this is a bug is there a workaround?

Thanks for replies

Michael

[support-michael]

Deployment of dependent projects along with a primary WEB, EJB, or EAR project is currently in development and should be released in the near future. Until then you should manually export your dependent utility projects as jars into EAR project. Jars in the EAR project will be deployed but you still have to maintain Class-path entries in your MANIFEST.MF until we complete this feature.

Michael
MyEclipse Support

[Brice Ruth]

@support-michael wrote:

Deployment of dependent projects along with a primary WEB, EJB, or EAR project is currently in development and should be released in the near future. Until then you should manually export your dependent utility projects as jars into EAR project. Jars in the EAR project will be deployed but you still have to maintain Class-path entries in your MANIFEST.MF until we complete this feature.

Michael
MyEclipse Support

Just to be clear, then – the JARs should be placed in the root of your EAR project, and the MANIFEST.MF file to be updated with the names of the JARs should be that in the EAR? Or do the individual MANIFEST.MF files in each of the EJB projects need to be updated as well?!

Any guidance is most welcome.

TIA
Brice Ruth

[Scott Anderson]

You need to update the MANIFEST.MF files in each of the EJB projects such that the Class-Path entry will include all library jars. A good example is available here:
http://java.sun.com/developer/Books/javaprogramming/JAR/basics/manifest.html

[Author]

Posts