• Post Reply Bookmark Topic Watch Topic
  • New Topic

using manifest.mf class-path

 
shail nig
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
m having ear file conataining 4 components
1.war
2.war
3.jar
4.jar
out of which 3.jar and 4.jar are EJB's
in manifest file of 3.jar i have placed following line for extension jar "5.jar"
Class-path: META-INF/lib/5.jar
and placed 5.jar in META-INF/lib directory before creating 3.jar.
when deploying on wls7 it gives one of the class not found error.
any one ot help on this one??
 
Ade Barkah
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Seems fine at first glance, but hard to tell from your description. Some things to check:
1. Is 5.jar in 3.jar's META-INF/lib or in the EAR's META-INF/lib? It should be the latter, i.e., *outside* 3.jar, directly within the EAR.
2. Unpack 3.jar manually after creating it and verify the MANIFEST.MF is still correct (it's easy to overwrite it with the default manifest file.) There should be a Manifest-Version plus the Class-path declaration.
3. Try simplifying things to start; e.g., put 5.jar directly at the EAR's root (same level with the rest of the wars/jars) and use "Class-path: 5.jar" in 3.jar's manifest.mf.
If all still fail, put the jar somewhere we can download, easier for us to decipher what's wrong that way.
-Ade Barkah
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!