PQ53180: THE GETCLASSLOADER METHOD WAS NOT ADDED BY WEBSPHERE


APAR

APAR status
Closed as program error.

Error description
Customers JSP includes a <%@ page extends which
spec states that the extends mechanism is available
for sophisticated users and it should be used with extreme
care as it restricts what some of the decisions that a JSP
container can take.  However customer still wishes to use
extends and the getClassLoader method was not added by
websphere. This does not fully comply with j2ee spec.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 3.5.4 and 3.5.5 *
*                 developers using jsp 1.1 and implementing    *
*                 their own HttpJspPage with useBean tags.     *
****************************************************************
* PROBLEM DESCRIPTION: JSP fails to compile when customer      *
*                      uses extends directive in jsp page      *
*                      for jsp 1.1.  The customer wants        *
*                      to implement their own                  *
*                      implementation of HttpJspPage.          *
*                      Error message: method                   *
*                      getClassLoader() not found in           *
*                      <jsp_name>.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The version of Jasper that WebSphere originally ported
to WAS 3.5.2 contained a method called getClassLoader()
that was needed to instantiate beans.  This method is
not required by the jsp1.1 specification and caused
compile time failures for customers wishing to implement
their own HttpJspPage who did not implement this method.
Since the specification did not require this method
to be implemented, WebSphere was not implementing jsp1.1
according to specification.
Problem conclusion
Since WebSphere requires the method getClassLoader for it's
implementation of HttpJspPage, WebSphere now checks for the
existence of the extends directive. If customer implements
their own HttpJspPage, change the instantiation to not rely
on the existence of getClassLoader implemented by WebSphere.
Temporary fix
pq53180_354.jar --> for current customer (ptf  4 level)
pq53180_355.jar --> for customers after the release of ptf5.
Comments
APAR information
APAR numberPQ53180
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-10-05
Closed date2001-10-16
Last modified date2001-12-17

APAR is sysrouted FROM one or more of the following:

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

PQ53310

Modules/Macros
JSP
APAR is sysrouted TO one or more of the following:PQ53310Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ53180
IBM Group: Software Group
Modified date: 2001-12-17