3 Replies Latest reply on Aug 22, 2003 2:43 PM by kprindia

    EJBDeployer handling of MANIFEST.MF broken in 3.2.1?

    troypoppe Newbie

      I just installed 3.2.1 (upgrading from 3.0.6) and I think I've discovered a problem with the EJBDeployer's handling of META-INF/Manifest.MF files.

      In an EAR file I had working on 3.0.6, I had the following contents of a Manifest.MF:

      Manifest-Version: 1.0
      Ant-Version: Apache Ant 1.5.2
      Created-By: 1.4.1_01-b01 (Sun Microsystems Inc.)
      Class-Path: lib/Party.jar

      When deployed on 3.0.6, this worked fine, and added the path (from inside the ear file) to the classpath, and loaded the classes properly.

      However, in 3.2.1, I get this error message when deploying:

      13:58:10,431 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.2.1/server/default/deploy/pmsejb.ear
      13:58:10,451 INFO [EARDeployer] Init J2EE application: file:/C:/jboss-3.2.1/server/default/deploy/pmsejb.ear
      13:58:10,982 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.2.1/server/default/deploy/pmsejb.ear references URL file:/C:/jboss-3.2.1/server/default/deploy/lib/Party.jar which could not be opened, entry ignored
      13:58:12,384 WARN [EJBDeployer] Verify failed; continuing

      Note the path it is trying to load from, this is not relative to the archive (.ear). This seems to be a violation of the jar file specification (http://java.sun.com/j2se/1.4.1/docs/guide/jar/jar.html#JAR%20Manifest)

      Any guidance?


      Troy Poppe