PQ63036: AFTER APPLYING EFIX PQ55090 APPLICATION THROWING COM.SUN.JSP.JSPEXCEPTION WITH JSP 1.0 PROCESSOR IS USED.

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
AFTER APPLYING EFIX PQ55090, APPLICATION THROWING JSP 1.0
PROCESSOR COMPILE EXCEPTIONS. com.sun.jsp.JspException.
After upgrade from WAS 3.5.3 to WAS 3.5.6, JSP 1.0 compatibility
mode, JSP compilation errors thrown. The same JSP works fine in
WAS 3.5.3. The APAR PQ55090 is causing this exception. PQ55090
is included in WAS 3.5.6
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server developers      *
*                 using jsp 1.0 and useBean tags.              *
****************************************************************
* PROBLEM DESCRIPTION: JSP useBean tags fail to compile        *
*                      when bean instance is an abstract       *
*                      class, interface or a class without     *
*                      a zero argument constructor.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After applying PQ55090, WebSphere fails to adhere to
the jsp specification with regards to instantiation of
java beans using the <jsp:useBean /> tag.

----------- JSP SPEC 1.0 ------------------
ftp://ftp.java.sun.com/pub/jsp/798flk/jsp1_0-spec.pdf
Section 2.13.1

5. If the object is not found in the specified scope; and the
class specified names a nonabstract class that defines a
public no-args constructor, then that class is instantiated,
and the new object reference is associated the with the
scripting variable and with the specified name in the
specified scope using the appropriate scope dependent
association mechanism (see PageContext). After this, step 7
is performed.
-----------------------------------------------
Problem conclusion
The customer that requested the APAR for the original defectPQ55090, misinterpeted the specification.  However, since
the behavior change request was accepted by L3 Support,
the behavior will not be removed.  To enable the original
behavior requested in PQ55090, do the following...

<WAS_ROOT>/properties/global.properties (create if needed)
add line --> com.sun.jsp.useBeanConstructorMethod=true

This APAR will return the default behavior for <jsp:useBean/>
to the way 3.5.5 and earlier releases worked for jsp 1.0.
Temporary fix
//wasdoc0/apars/pq63036/3.5.6
Comments
APAR information
APAR numberPQ63036
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-07-10
Closed date2002-07-11
Last modified date2002-07-22

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:


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

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ63036
IBM Group: Software Group
Modified date: 2002-07-22