You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by pi...@locus.apache.org on 2000/10/11 07:08:08 UTC
cvs commit: jakarta-tomcat-4.0/jasper/doc/dev ModifsForFlushFalse.html TODO.html status.html
pierred 00/10/10 22:08:07
Modified: . NEW_SPECS.txt
jasper/doc/dev TODO.html status.html
Added: jasper/doc/dev ModifsForFlushFalse.html
Log:
Updated the docs to reflect the implementation of the
new JSP1.2 feature: <jsp:include ... flush="false">
Revision Changes Path
1.5 +3 -3 jakarta-tomcat-4.0/NEW_SPECS.txt
Index: NEW_SPECS.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/NEW_SPECS.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- NEW_SPECS.txt 2000/10/04 02:26:25 1.4
+++ NEW_SPECS.txt 2000/10/11 05:08:05 1.5
@@ -3,7 +3,7 @@
New Spec Features Implementation
================================
-$Id: NEW_SPECS.txt,v 1.4 2000/10/04 02:26:25 craigmcc Exp $
+$Id: NEW_SPECS.txt,v 1.5 2000/10/11 05:08:05 pierred Exp $
Introduction
@@ -90,8 +90,8 @@
JavaServer Pages (JSP) Specification, version 1.2
=================================================
-JSP Include Supports flush="false" [Rare]
------------------------------------------
+JSP Include Supports flush="false" [Medium]
+-------------------------------------------
This change will allow use of <jsp:include> nested within another standard
or custom tag, allowing the output produced by the included servlet (or
page) to be buffered and processed. This change depends on the enhancement
1.5 +3 -0 jakarta-tomcat-4.0/jasper/doc/dev/TODO.html
Index: TODO.html
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/jasper/doc/dev/TODO.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- TODO.html 2000/09/26 17:46:01 1.4
+++ TODO.html 2000/10/11 05:08:06 1.5
@@ -39,6 +39,9 @@
a wrapped response, to be passed as the second argument to the internal
RequestDispatcher.include() that implements this element, which grabs all
the output text and copies it to the current JspWriter.
+<p>
+First implementation committed 2000/09/18.
+<a href="ModifsForFlushFalse.html">Summary of Changes</a>.<p>
<h3>Made the XML view of a JSP page available for input, and for validation</h3>
This is one of the main issues that has motivated the need
1.5 +9 -1 jakarta-tomcat-4.0/jasper/doc/dev/status.html
Index: status.html
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/jasper/doc/dev/status.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- status.html 2000/09/26 17:46:02 1.4
+++ status.html 2000/10/11 05:08:06 1.5
@@ -8,7 +8,7 @@
<h1>Status of Jasper</h1>
The goal of this document is to keep everyone informed of the major developments
happening with Jasper.<br>
-<i>$Id: status.html,v 1.4 2000/09/26 17:46:02 pierred Exp $</i>
+<i>$Id: status.html,v 1.5 2000/10/11 05:08:06 pierred Exp $</i>
<h2>Current Status</h2>
Trying to bootstrap the work required to bring Jasper in compliance
@@ -19,6 +19,14 @@
<h2>History</h2>
<ul>
+<li>2000/10/10
+<br>First commit of changes to support the following JSP1.2 addition
+to the API:
+<br>
+<i>jsp:include can now indicate flush="false"</i>
+<br>
+<a href="ModifsForFlushFalse.html">Summary of Changes</a>.<p>
+
<li>2000/09/26
<br>First commit of changes to support the following JSP1.2 addition
to the API:
1.1 jakarta-tomcat-4.0/jasper/doc/dev/ModifsForFlushFalse.html
Index: ModifsForFlushFalse.html
===================================================================
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<title>Modifications to support flush="false" in jsp:include</title>
</head>
<body>
<h1><jsp:include ... flush="false" > </h1>
<hr>
<h2>Classes Modified</h2>
<h3>IncludeGenerator</h3>
<ul>
<li>flush is not a required parameter anymore. Default value is "false".
<li>generated code now flushes the buffer or not prior to calling
pagecontext.include() depending on the flush value
</ul>
<h3>PageContextImpl</h3>
<ul>
<li>set the value of isIncluded when the page context is initialized
include()
<li>flush in an include is not done in pageContext anymore.
This is handled prior to calling the include() so we can flush or not
depending on the value of the flush attribute.
<li>A ServletResponseWrapperInclude object is now passed as the Response
(the including page JspWriter is what gets returned in getWriter())
release()
<li>if isIncluded()
<ul>
<li> flush the current jspWriter into the including
page JspWriter
</ul>
<li>else
<ul>
<li> flush through (recursive) the buffer
</ul>
</ul>
<h3>JspParseEventListener</h3>
<ul>
<li>generateFooter(): do not generate the code to flush the buffer anymore
this will be handled in pageContext.release() which will
flush the buffer in a way that depends whether the
page is being included or not.
</ul>
<h3>messages.properties</h3>
<ul>
<li>add jsp.error.include.flush.invalid.value
</ul>
<h2>New files</h2>
<H3>ServletResponseWrapperInclude</h3>
<hr>
<h2>Issues</h2>
Implementation of this new feature has brought up a few issues
which have been submitted to the expert group. Implementation will
be revised once we get clarifications.
<p>
Specifically:
<ul>
<li>A forward done in an included page yields an infinite
loop because the jsp engine has no way of knowing that the
include request attributes should be ignored.
<li>Not clear what the impact of a forward performed within an
included page should be on the output buffers.
</ul>