PH54218: GET JAR PLACED INTO BOTH THE EAR AND WAR CLASS LOADER

APAR status

• Closed as new function.

Error description

• Allow loose applications that utilize the same virtual path to
  represent a jar in both WEB-INF/lib and the WAR's manifest class
  path to successfully get that jar placed into both the EAR and
  WAR class loader
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  running with "resources in workspace" in a  *
  *                  development environment                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: A jar placed in both a web module and   *
  *                      that module's dependency class path is  *
  *                      not included in both the EAR and WAR    *
  *                      class paths                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When running in a development environment with "resources in
  workspace" (also known as a "loose archive" - the application is
  not packaged into an EAR file and deployed on the server), a jar
  file that is included separately within a web module (e.g. in
  WEB-INF/lib) and in the web module's manifest class path is
  detected by the class loader as the same file, and not added to
  the EAR and WAR class paths. In practice, even though those jars
  point to the same location in the development environment, they
  would be two separate file paths when built into an EAR (one in
  the EAR itself, one in the WAR), so they should be added to both
  the EAR and WAR class loaders.
  

Problem conclusion

• This change allows the addition of duplicate paths to a module's
  dependency class path in "loose archive" scenarios.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.24 and 9.0.5.17. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels