PQ72658: The MANIFEST.MF Class Path Entry in a jar file in a Shared Library is not resolved.

 A fix is available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
The MANIFEST.MF Class Path Entry in a .jar file in a Shared
Library is not resolved and the classes are not loaded by the
Application Class Loader.

SCENARIO:
I have a .jar file with a MANIFEST.MF Class Path entry as
specified
in Extension Mechanism Architecture (available at

http://java.sun.com/j2se/1.3/docs/guide/extensions/spec.html)
and I create a Shared Library that contains the .jar file in
it's Class Path entry as shown in the libraries.xml below:

<?xml version="1.0" encoding="UTF-8"?>
<libraries:Library xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:libraries="http://www.ibm.com/websphere/appserver/schemas/
5.0/libr
aries.xmi" xmi:id="Library_1" name="DepJars">
  <classPath>C:\PMRTEST\dependency2.jar</classPath>
</libraries:Library>

The Shared Library is then associated with an application so the
classes
Local fix
will be lo ded by the application classloader as shown in the
deployment.xml below:

<appdeployment:Deployment .....>
...
    <classloader xmi:id="Classloader_1" mode="PARENT_FIRST">
      <libraries xmi:id="LibraryRef_1" libraryName="DepJars"/>
    </classloader>
...
</appdeployment:Deployment>
LOCAL FIX:&#65437;
none
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 shared libraries                             *
****************************************************************
* PROBLEM DESCRIPTION: The MANIFEST.MF Class-Path Entry in a   *
*                      jar file in a shared library is not     *
*                      resolved.  Thus classes in the shared   *
*                      library may not be found even though    *
*                      they exist.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere classloader for shared libraries was not
processing the Class-Path entries in the manifest.  Thus
only the explicitly configured jar file(s) were being
added to the shared library's classpath.
Problem conclusion
Added additional code to the classloader to detect
and incorporate Class-Path entries in the manifests
of shared library jar files.
Temporary fix
I have provided an efix.
Comments
APAR information
APAR number PQ72658
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-03-31
Closed date 2003-07-16
Last modified date 2003-07-16

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
CLASSLDR          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ72658
IBM Group: Software Group
Modified date: Jul 16, 2003