[Clay]

Ok, I’m using weblogic 7.0 SP4 as my app server. I’ve got a regular java project referenced in my web module. When I deploy at the enterprise application level, it jars up the dependent directory and places the file at the root of the application.

if I right-click on the enterprise application, select MyEclipse and then select New Module Manifests, it creates a classpath entry with the same jar that’s being placed at the root of the application.

this is all as it should be.

my problem is that after deployment, i’m getting a no-class-def-found exception when trying to access a file in that directory. Any idea what the problem could be?

I’m using Eclipse 3.0.1
MyEclipse 3.8.4
JDK is 1.5 for eclipse and 1.4.2 for weblogic.

[Clay]

Seems as though the manifest generator doesn’t put a ” ” after the Manifest-Version line and it screws weblogic up.

[Riyad Kalla]

Clay can you post the busted MANIFEST adn the corrected one for comparison? I’ll file this asap.

[Author]

Posts