PQ59243: FLUSH IS PERFORMED WHEN INCLUDING INSIDE JSP BODY TAG.

APAR status
Closed as program error.

Error description
It is not possible to perform an include inside a JSP body tag
since (per the java doc) on JSP 1.1, both jsp:include and
pageContext.include perform a flush.
JSP gets the following error:
java.io.IOException: Illegal to flush within a custom tag
The customer needs to be able to perform an include from
within a JSP body tag.  This function is available in JSP1.2
shipped with WebSphere 5.0.
JSP tag body websphere
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Developers using       *
*                 jsps containing custom tags.                 *
****************************************************************
* PROBLEM DESCRIPTION: Including to other resources inside a   *
*                      jsp custom tag throws the               *
*                      exception "java.io.IOException:         *
*                      Illegal to flush within a custom tag".  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Using the provided jsp include mechanisms inside of a custom
tag (body tag) is throwing an IOException.  According to the
Java API documentation and JSP 1.1 Specification, both
<jsp:include /> (explicit) and pageContext.include (implicit)
flush the outputstream.  The JSP 1.1 specification also states
that <jsp:includes /> are illegal from within custom tags
of type body tag.
Problem conclusion
Since WebSphere changed behavior with regards to body tags
and flushing of outputstreams during a ptf cycle, a new flag
has been added to permit flushing within body tags.
Setting the following jvm system property will enable the
original behavior.
name =  com.ibm.jsp.bodytag.ignore.flush  value =  true
Customers should be aware that this behavior is against
the jsp specification but for backwards compatibility
WebSphere is permitting this behavior.
Temporary fix
//wasdoc0/apars/pq59243/4.0.2
Comments
APAR information
APAR number PQ59243
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-03-20
Closed date 2002-04-02
Last modified date 2002-04-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JSP          

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ59243
IBM Group: Software Group
Modified date: Apr 2, 2002