aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes difference between Classpath setting in Manifest file and AppServer classpath Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "difference between Classpath setting in Manifest file and AppServer classpath " Watch "difference between Classpath setting in Manifest file and AppServer classpath " New topic
Author

difference between Classpath setting in Manifest file and AppServer classpath

sathish kannan
Greenhorn

Joined: Jul 11, 2002
Posts: 29
Can anyone please tell me the difference of setting the classpath in Manifest file of our application's ear file and the weblogic App server's classpath
thanks in advance
sathish
Dave Landers
Ranch Hand

Joined: Jul 24, 2002
Posts: 401
The system classpath is available to all code running on the server.
If you put something in an ejb's Manifest Class-Path, then that jar is accessible only to that ejb. Actually, the way WebLogic's ClassLoaders are set up, that jar will be accessible to all ejbs and webapps in the application.
If you put a jar in WEB-INF/lib or in the webapp's manifest, it is only accessible to servlets, jsps, tags, etc in that webapp.
I don't think the EAR's manifest is considered (at least the spec doesn't require it and WebLogic doesn't look at it).
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: difference between Classpath setting in Manifest file and AppServer classpath