]
Scott M Stark updated JBAS-3883:
--------------------------------
Fix Version/s: JBossAS-5.0.0.Beta3
JBoss ignores "Class-Path" attribute in WAR's
MANIFEST.MF
---------------------------------------------------------
Key: JBAS-3883
URL:
http://jira.jboss.com/jira/browse/JBAS-3883
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service, ClassLoading
Affects Versions: JBossAS-5.0.0.Beta1
Reporter: Amit Kasher
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
An EAR file that deploys well in JBoss4.0.5 fails to deploy in JBoss5.0Beta1 when
initializing the web application (NoClassDefFound).
However, this ear does deploy well when taking the required jar files (the WAR
dependencies) out of the EAR and placing them inside the .war/WEB-INF/lib folder, as well
as removing the "Class-Path" entry in the WAR's MANIFEST.MF.
Documents stating, as far as I understand, the existence of the requirement that this
should work are here:
http://java.sun.com/j2ee/verified/packaging.html
... as well as in the spec ... (
http://jcp.org/en/jsr/detail?id=244) in section EE.8.2.1
(Bundled Libraries) starting in page 155.
It's related to Tomcat's classpath (or to the classpath augmentation JBoss
performs, where there were probably recent changes to support resource injection into web
clients, like servlets). This is why I indicated Tomcat as an additional affected
component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: