I have just read this over the net, do you think it has anything to do with my problem?
Support for the extension mechanism does not exist for EAR, WAR, or RAR applications as defined in the J2EE specification, since these applications are not directly loaded by a ClassLoader instance. Web applications still have to have libraries packaged in the WEB-INF\lib directory and resource-adapter applications can have libraries bundled directly in the RAR file. Enterprise applications will need to package any libraries within the Web, EJB, or resource-adapter application that requires them. So how does the extension mechanism work with EJB applications? A JAR file can reference a dependent JAR file by adding a Class-Path manifest attribute. The Class-Path manifest attribute lists the relative URLs to search for utility libraries. Multiple URLs can be specified in a single Class-Path entry and a single JAR file can contain multiple Class-Path entries. For example, a JAR file might have:
In fact I tried as well to perform something much much simpler (refrecing a jar from the manifest.mf and it didnt work) here is what I performed:
deploy / tomer.war
deploy / tomer.war / common.jar
deploy / tomer.war / index.jsp (importing a class from common.jar)
deploy / tomer.war / WEB-INF / web.xml
deploy / tomer.war / META-INF / MANIFEST.MF
Ant-Version: Apache Ant 1.5.4
Created-By: 1.4.1_06-b01 (Sun Microsystems Inc.)
Now I received package not exist for the imported class's package!
How is it then possible to reference a jar from the manifest.MF ???
(Note that if I place the jar under WEB-INF/lib everythign is fine ofcourse, but that is not my meaning)