PQ57530: WHEN USING NAMEDDISPATCHER TO CALL A JSP IT FAILS WITH A 404 ERROR | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description When using NamedDispatcher to call a JSP it fails with 404 error WebSphere V4 request.getUserPrincipal() throws NullPointerException in a named dispatchLocal fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server developers * * using WebAppNamedDispatcher. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere returns a 404 error when * * attempting to dispatch to a jsp using * * WebAppNamedDispatcher. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebAppNamedDispatcher is unable to dispatch to a jsp that is defined in the web.xml as a jsp mapped servlet. This Servlet 2.2 requirement was not implemented in the current release of the product.Problem conclusion To meet the Servlet 2.2 requirement for jsp mapped servlets, changed behavior of WebAppNamedDispatcher to match that of the more common WebAppRequestDispatcher.Temporary fix //wasdoc0/apars/pq57530/4.0.2Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ57530
IBM Group: Software Group
Modified date: Feb 7, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.