View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820293#3820293
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820293 I scanned quickly j2ee 1.3 specification. It does not deny deploying modules through manifest file. Nor does it require the container to do so. The 1.4 spec is much more detailed and easier to understand than the 1.3. The 1.3 spec says: If the module is a type that contains JAR format files (for example, web and Connector modules), all classes in .jar files within the module referenced from other JAR files within the module using the Class-Path manifest header must be included in the deployment. and in an another section: All classes in .jar files referenced from other JAR files using the Class-Path manifest header must be included in the deployment. uh.. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user