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/18 01:00:12 UTC
cvs commit: jakarta-tomcat-4.0/jasper/doc/dev ModifsForIterationTag.html TODO.html status.html
pierred 00/10/17 16:00:11
Modified: jasper/doc/dev TODO.html status.html
Added: jasper/doc/dev ModifsForIterationTag.html
Log:
Docs update.
Revision Changes Path
1.6 +5 -1 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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- TODO.html 2000/10/11 05:08:06 1.5
+++ TODO.html 2000/10/17 23:00:10 1.6
@@ -67,7 +67,7 @@
First implementation committed 2000/09/18.
<a href="ModifsForXJsp.html">Summary of Changes</a>.<p>
-<h3>New IteratorTag interface to support iteration without BodyContent</h3>
+<h3>New IterationTag interface to support iteration without BodyContent</h3>
In JSP 1.1, your custom tag must implement BodyTag if it wants to support
iteration. In many simple cases where the nested content of a tag is just
reprocessed by the iteration anyway, it would be nice to allow a custom tag
@@ -78,6 +78,10 @@
This should require fairly minor changes to the generated
code for a page using custom tags. Updated support classes will already be
part of the API.
+
+<p>
+First implementation committed 2000/10/17.
+<a href="ModifsForIterationTag.html">Summary of Changes</a>.<p>
<h3>Added listener classes to the TLD</h3>
With the advent of application events support in Servlet 2.3, it is
1.6 +10 -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.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- status.html 2000/10/11 05:08:06 1.5
+++ status.html 2000/10/17 23:00:10 1.6
@@ -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.5 2000/10/11 05:08:06 pierred Exp $</i>
+<i>$Id: status.html,v 1.6 2000/10/17 23:00:10 pierred Exp $</i>
<h2>Current Status</h2>
Trying to bootstrap the work required to bring Jasper in compliance
@@ -19,6 +19,15 @@
<h2>History</h2>
<ul>
+
+<li>2000/10/17
+<br>First commit of changes to support the following JSP1.2 addition
+to the API:
+<br>
+<i>New IterationTag interface to support iteration without BodyContent</i>
+<br>
+<a href="ModifsForIterationTag.html">Summary of Changes</a>.<p>
+
<li>2000/10/10
<br>First commit of changes to support the following JSP1.2 addition
to the API:
1.1 jakarta-tomcat-4.0/jasper/doc/dev/ModifsForIterationTag.html
Index: ModifsForIterationTag.html
===================================================================
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<title>Modifications to support IterationTag in JSP</title>
</head>
<body>
<h1>IterationTag support</h1>
<hr>
<h2>Classes Modified</h2>
<h3>TagBeginGenerator</h3>
<ul>
<li>The return value of doStartTag() is now checked against EVAL_BODY_BUFFERED
instead of EVAL_BODY_TAG.
EVAL_BODY_TAG is deprecated, and both have the same integer value
so we only check against EVAL_BODY_BUFFERED.
</ul>
<h3>TagEndGenerator</h3>
<ul>
<li>doAfterBody() is now called if tag is an instance of IteratorTag (instead
of if it is an instance of BodyTag)
<li>The return value of doAfterBody() is now checked against EVAL_BODY_AGAIN
instead of EVAL_BODY_TAG.
EVAL_BODY_TAG is deprecated, and both have the same integer value
so we only check against EVAL_BODY_AGAIN.
</ul>