You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@locus.apache.org on 2000/07/11 17:46:43 UTC
cvs commit: xml-xalan/xdocs/sources/design design1_1_0.xml
dleslie 00/07/11 08:46:42
Modified: xdocs/sources/design design1_1_0.xml
Log:
Added link to xalan-j 2.0 javadoc
Revision Changes Path
1.2 +14 -12 xml-xalan/xdocs/sources/design/design1_1_0.xml
Index: design1_1_0.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/design/design1_1_0.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- design1_1_0.xml 2000/04/21 14:17:14 1.1
+++ design1_1_0.xml 2000/07/11 15:46:39 1.2
@@ -1,21 +1,23 @@
<?xml version="1.0"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-<s1 title="Xalan-J 1.1.0 Design">
- <p><link>Xalan-J 1.1.0 Design</link><img src="xmllogo.gif" alt="xmllogo.gif"/></p>
+<s1 title="Xalan-J 2.0 Design">
+ <p><link>Xalan-J 2.0 Design</link><img src="xmllogo.gif" alt="xmllogo.gif"/></p>
<ul>
<li>Author: Scott Boag</li>
- <li>State: In Progress</li>
- </ul>
+ <li>State: In Progress</li>
+ <li><jump href="http://xml.apache.org/xalan-j/apidocs/index.html">Xalan-J 2.0 Javadoc</jump></li>
+ </ul>
<s2 title="Introduction">
<p><link>Introduction</link></p>
- <p>This document presents the basic design for Xalan-J 1.1.0, which is a
+ <p>This document presents the basic design for Xalan-J 2.0, which is a
<jump href="http://www.awl.com/cseng/titles/0-201-89542-0/techniques/refactoring.htm">refactoring</jump>
- and redesign of the Xalan-J 1.0.1 processor. The main goals of this redesign are
+ and redesign of the Xalan-J 1.x proces
+ sor. The main goals of this redesign are
to: </p>
<ol>
<li>Make the design and code more understandable by Open Source
people.</li>
- <li>Reduce code size and complexity.</li>
+ <li>Reduce code size and complexity.</li>
<li>By simplifying the code, make optimization easier.</li>
<li>Make modules generally more localized, and less tangled with other
modules.</li>
@@ -51,7 +53,7 @@
</s2>
<s2 title="Overview of Architecture">
<p><link>Overview of Architecture</link></p>
- <p>Xalan 1.1.0 is divided into four major modules, and various smaller
+ <p>Xalan 2.0 is divided into four major modules, and various smaller
modules. The main modules are:</p>
<gloss>
<label><code><link anchor="process">org.apache.xalan.process</link></code></label>
@@ -116,7 +118,7 @@
<gloss>
<label><code><link anchor="xxx">org.apache.xalan.xslt</link></code></label>
<item>This package is for backwards compatibility with applications that
- depend on Xalan 1.0.x interfaces.</item>
+ depend on Xalan 1.x interfaces.</item>
</gloss>
</s2><anchor name="process"/>
<s2 title="Process Module">
@@ -404,7 +406,7 @@
</s2><anchor name="xpath"/>
<s2 title="XPath Module">
<p><link>XPath Module</link></p>
- <p>(This module for the most part remains the same in 1.1.0)</p>
+ <p>(This module for the most part remains the same in 2.0)</p>
</s2>
<s2 title="Utils Package">
<p><link>Utils Package</link></p>
@@ -453,8 +455,8 @@
to be solved.)</p>
<gloss>
<label>Space stripping</label>
- <item>In Xalan 1.0.0, it is clear that space stripping was a major
- performance issue. This needs to be solved in Xalan 1.1.0 by stripping the
+ <item>In Xalan 1.x, it is clear that space stripping was a major
+ performance issue. This needs to be solved in Xalan 2.0 by stripping the
space nodes as the document is being parsed. This is a major problem though for
DOM trees. This can be perhaps be solved by preprocessing the DOM tree and
creating a table of space-stripping parent elements, when the nodes can't be