1 Reply Latest reply on Oct 29, 2010 11:31 AM by titou09

    WebSphere deployment doc bug for strategy 2



      I believe I have found a new bug in documentation describing WebSphere application deployment using strategy 2. See snapshot WebSphere doc or 2.2.1.CR2 WebSphere doc.

      Documentation states: To use this strategy: Add a file named META-INF/ibm-ejb-jar-ext.xml in the EJB module and add an entry for each session bean like this: and proceeds with example of how such file could look like.

      The error is in the name of the file. It should be ibm-ejb-jar-bnd.xml not ibm-ejb-jar-ext.xml. When using incorrect name ibm-ejb-jar-ext.xml, WebSphere 7 EAR deployment will fail with message:

      The exception com.ibm.websphere.management.application.client.AppDeploymentException: Unexpected exception. [Root exception is org.eclipse.jst.j2ee.commonarchivecore.internal.exception.ResourceLoadException: IWAE0007E Could not load resource "META-INF/ibm-ejb-jar-ext.xml" in archive "??????.jar"] occurred. Check log for details.

      where ??????.jar references the ejb jar file in which ibm-ejb-jar-ext.xml is contained.

      When I rename the file to ibm-ejb-jar-bnd.xml no error is reported and WebSphere allows me to continue deploying EAR.