PQ46151: APPLYING EFIX 3.5.2 REQUIRES CHANGES TO CUSTOMER CODE


APAR

APAR status
Closed as documentation error.

Error description
Problem: The customer applied efix 3.5.2. The customers app now
fails with the message AbstractMethodError or AbstractClassError
Further discussion shows that the source of these errors comes f
rom thewebsphere implementation of the servlet 2.2. spec and the
fact that customers code was created for the servlet 2.1 spec.
Since fixpack 3.5.2 was applied as an efix the customer did not
expect any requirement to change his code to comply with
webspheres implemention of the servlet 2.2. spec.
From L3 we need 1 of 2 things, either websphere 3.5.2 needs to
allow for the use of classes and methods defined in the 2.1
spec or, we need to present documentation to the customer
specifying the methods and classes which have changed, and how
the customer should modify their code to allow for these changes
Note:
The customer had their own implementation of the servlet 2.1.
HttpSession, HttpServletRequest and HttpServletResponse classes
Note:The customer had their own implementation of the servlet 2.1.HttpSession, HttpServletRequest and HttpServletResponse classes
Local fix
Problem summary
WebSphere made a change at 3.5.2 to implement
the servlet 2.2 spec.  In order to maintain compatibility with
existing WebSphere applications, the servlet engine can run in
either compatibility mode or compliance mode.  Compatibility
mode allows behavior consistent with the existing applications
at the expense of compliance with the Servlet 2.2 specification.
In 3.5.2, WebSphere is always running to the servlet 2.2 spec.
In compatibility mode, behavioral changes are made to support
existing applications written to the 2.1 spec.  Note, in 3.5.2
we ONLY ship the 2.2 API's, compatibility mode is not an
implementation of the 2.1 spec.
In the problem being reported here, the application has been
written to the servlet 2.1 spec and the API has been extended.
Since the customer has extended the API, the application will
need to be upgraded to the new servlet 2.2. spec, as
compatibility mode will not provide the expected results.
For full details of what has changed in the servlet spec,
please see http://java.sun.com/products/servlet/index.html
The Java Servlet Specification 2.2 can be downloaded, and all
the new methods will be found in bold type.
Problem conclusion
Closing doc.
Temporary fix
Comments
APAR information
APAR numberPQ46151
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED DOC
PENoPE
HIPERNoHIPER
Submitted date2001-02-14
Closed date2001-02-17
Last modified date2001-02-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:


Modules/Macros

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

Applicable component levels











Document Information

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