PQ58576: ERROR 404 RAISED WHEN USING JSP:INCLUDE TAG TO INCLUDE ANOTHER JSP FILE | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description A JSP file uses the jsp:include tag to include another JSP, and the page=<url> attribute is set to a URL that results in the invocation of a servlet. The invoked servlet then uses the Request Dispatcher to include the second JSP based on its URI. The constructed URL for the include shows the URI for the second JSP file twice, which results in a 404 (page not found) exception when trying to dispatch the URI. For example, the URI should be: . /Page2.jsp . but instead it is converted to . /Page2.jsp/Page2.jsp . which results in the 404 exception. . This behavior in WAS 4.0.2 AE is a regression from WAS 4.0.1 AE. The JSPs and servlet run to successful completion with WAS 4.0.1.Local fix Customer architecture requires the invocation of the servlet that uses the RequestDispatcher, so there is currently no workaround for the problem.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 using JSP * * and doing dynamic includes to another JSP * * or a servlet. * **************************************************************** * PROBLEM DESCRIPTION: JSP's doing a dynamic include to * * another jsp or servlet fails with a * * FileNotFoundException 404 HTTP Error * * code * **************************************************************** * RECOMMENDATION: * **************************************************************** A JSP file uses the jsp:include tag to include another JSP, and the page=<url> attribute is set to a URL that results in the invocation of a servlet. The invoked servlet then uses the Request Dispatcher to include the second JSP based on its URI. The constructed URL for the include shows the URI for the second JSP file twice, which results in a 404 (page not found) exception when trying to dispatch the URI. For example, the URI should be: . /Page2.jsp . but instead it is converted to . /Page2.jsp/Page2.jsp . which results in the 404 exception. .Problem conclusion The URL is formed correctly by clearing and setting the parameters after an include or forward to a jsp or servlet so that it finds the required resource as expected.Temporary fix PQ58576 is on wasdoc0Comments
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 #: PQ58576
IBM Group: Software Group
Modified date: Sep 30, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.