cziegeler 01/09/19 01:50:46
Modified: xdocs logicsheet-concepts.xml uc2.xml xsp-internals.xml
Log:
Change the <jump> element to <link> element
and activate the Document Type Definition
Submitted by: David Crossley
Revision Changes Path
1.4 +16 -18 xml-cocoon2/xdocs/logicsheet-concepts.xml
Index: logicsheet-concepts.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/logicsheet-concepts.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- logicsheet-concepts.xml 2001/07/19 14:20:23 1.3
+++ logicsheet-concepts.xml 2001/09/19 08:50:46 1.4
@@ -1,8 +1,6 @@
<?xml version="1.0"?>
-<!--
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
--->
<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
<document>
@@ -22,26 +20,26 @@
<ul>
<li>
- <jump anchor="logicsheet">Logicsheets</jump>
+ <link href="#logicsheet">Logicsheets</link>
</li>
<li>
- <jump anchor="helper-classes">Logicsheet Helper Classes</jump>
+ <link href="#helper-classes">Logicsheet Helper Classes</link>
</li>
<li>
- <jump anchor="logicsheet-object">Logicsheets and Objects</jump>
+ <link href="#logicsheet-object">Logicsheets and Objects</link>
</li>
<li>
- <jump anchor="xsl-logicsheets">Logicsheets and XSLT</jump>
+ <link href="#xsl-logicsheets">Logicsheets and XSLT</link>
</li>
<li>
- <jump anchor="java-logicsheets">
+ <link href="#java-logicsheets">
XSLT Logicsheets and XSP for Java
- </jump>
+ </link>
</li>
<li>
- <jump anchor="logicsheet-language">
+ <link href="#logicsheet-language">
The SiLLy Logicsheet Language
- </jump>
+ </link>
</li>
</ul>
</s1>
@@ -66,7 +64,7 @@
They translate dynamic tags to <em>actual code</em> enclosed in
code-embedding directives. Fortunately, this dependency can be
alleviated by judiciously using
- <jump anchor="helper-classes">helper classes</jump>.
+ <link href="#helper-classes">helper classes</link>.
</p>
<p>
@@ -201,7 +199,7 @@
<p>
A brute-force logicsheet template may be implemented
- (in XSLT, as discussed <jump anchor="xsl-logicsheets">below</jump>)
+ (in XSLT, as discussed <link href="#xsl-logicsheets">below</link>)
as:
</p>
@@ -472,9 +470,9 @@
XSLT provides all the capabilities needed for dynamic markup
transformation as well for final code generation (described
in
- <jump href="xsp-internals.html" anchor="logicsheet-generator">
+ <link href="xsp-internals.html#logicsheet-generator">
Logicsheet Code Generators
- </jump>).
+ </link>).
</p>
<p>
@@ -517,9 +515,9 @@
<p>
Such language is described in detail below, under
- <jump anchor="logicsheet-language">
+ <link href="#logicsheet-language">
The SiLLy Logicsheet Language
- </jump>.
+ </link>.
</p>
<p>
@@ -697,7 +695,7 @@
<p>
This example shows clearly why we need a
- <jump anchor="logicsheet-language">SiLLy</jump>
+ <link href="#logicsheet-language">SiLLy</link>
language!
</p>
</s1>
@@ -821,7 +819,7 @@
<p>
SiLLy templates are much terser and easier to read and write than
the XSLT-based examples presented
- <jump anchor="complex-example">above</jump>:
+ <link href="#complex-example">above</link>:
</p>
<source><![CDATA[
1.11 +18 -20 xml-cocoon2/xdocs/uc2.xml
Index: uc2.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/uc2.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- uc2.xml 2001/09/18 07:22:52 1.10
+++ uc2.xml 2001/09/19 08:50:46 1.11
@@ -1,7 +1,5 @@
<?xml version="1.0"?>
-<!--
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
--->
<document>
<header>
<title>Understanding @Name@</title>
@@ -21,49 +19,49 @@
<ul>
<li>
- <jump anchor="pre-requisites">
+ <link href="#pre-requisites">
Prerequisites
- </jump>
+ </link>
</li>
<li>
- <jump anchor="a-little-history">
+ <link href="#a-little-history">
A Little History
- </jump>
+ </link>
</li>
<li>
- <jump anchor="what-problems">
+ <link href="#what-problems">
What problem does @docname@ solve?
- </jump>
+ </link>
</li>
<li>
- <jump anchor="basic-mechanisms">
+ <link href="#basic-mechanisms">
Basic Mechanisms.
- </jump>
+ </link>
</li>
<li>
- <jump anchor="c2-architecture">
+ <link href="#c2-architecture">
Architecture.
- </jump>
+ </link>
</li>
<li>
- <jump anchor="c2-abstractions">
+ <link href="#c2-abstractions">
Abstraction.
- </jump>
+ </link>
</li>
<li>
- <jump anchor="cocoon-configuration">
+ <link href="#cocoon-configuration">
@Name@ Configuration.
- </jump>
+ </link>
</li>
<li>
- <jump anchor="work-area">
+ <link href="#work-area">
@Name@ Work Area.
- </jump>
+ </link>
</li>
<li>
- <jump anchor="use-with-tomcat">
+ <link href="#use-with-tomcat">
Use with Tomcat
- </jump>
+ </link>
</li>
</ul>
</s1>
1.8 +34 -36 xml-cocoon2/xdocs/xsp-internals.xml
Index: xsp-internals.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/xsp-internals.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- xsp-internals.xml 2001/09/18 07:22:52 1.7
+++ xsp-internals.xml 2001/09/19 08:50:46 1.8
@@ -1,8 +1,6 @@
<?xml version="1.0"?>
-<!--
<!DOCTYPE document SYSTEM "./dtd/document-v10.dtd">
--->
<?xml-stylesheet href="document2html.xsl" type="text/xsl"?>
<document>
@@ -22,59 +20,59 @@
<ul>
<li>
- <jump anchor="markup-to-code">
+ <link href="#markup-to-code">
Markup-to-code Transformation
- </jump>
+ </link>
</li>
<li>
- <jump anchor="cocoon-generators">
+ <link href="#cocoon-generators">
XSP and @docname@ Generators
- </jump>
+ </link>
</li>
<li>
- <jump anchor="programming-language">
+ <link href="#programming-language">
The Programming Language Processor
- </jump>
+ </link>
</li>
<li>
- <jump anchor="compiled-languages">
+ <link href="#compiled-languages">
Compiled Languages
- </jump>
+ </link>
</li>
<li>
- <jump anchor="interpreted-languages">
+ <link href="#interpreted-languages">
Interpreted Languages
- </jump>
+ </link>
</li>
<li>
- <jump anchor="markup-language">
+ <link href="#markup-language">
The Markup Language Processor
- </jump>
+ </link>
</li>
<li>
- <jump anchor="xsp-language">
+ <link href="#xsp-language">
The XSP Markup Language
- </jump>
+ </link>
</li>
<li>
- <jump anchor="dom-xsp">
+ <link href="#dom-xsp">
The DOM-XSP Markup Language
- </jump>
+ </link>
</li>
<li>
- <jump anchor="program-generator">
+ <link href="#program-generator">
The Program Generator
- </jump>
+ </link>
</li>
<li>
- <jump anchor="named-components">
+ <link href="#named-components">
Named Components
- </jump>
+ </link>
</li>
<li>
- <jump anchor="sitemap-configuration">
+ <link href="#sitemap-configuration">
XSP Sitemap Configuration
- </jump>
+ </link>
</li>
</ul>
</s1>
@@ -145,7 +143,7 @@
<code>ServerPagesGenerator</code>,
</link>
a proxy that uses @docname@'s
- <jump anchor="program-generator"><code>ProgramGenerator</code></jump>
+ <link href="#program-generator"><code>ProgramGenerator</code></link>
component to load pages and subsequently delegates actual SAX event
generation to them.
</p>
@@ -237,7 +235,7 @@
<p>
The complete XSP sitemap configuration is explained
- <jump anchor="sitemap-configuration">below</jump>.
+ <link href="#sitemap-configuration">below</link>.
</p>
</s2>
@@ -268,7 +266,7 @@
is tested by <code>ProgramGenerator</code> to assert whether the page has
been invalidated as a result of files it depends on having changed on disk.
These files are typically
- <jump anchor="logicsheet"><em>logicsheets</em></jump>
+ <link href="#logicsheet"><em>logicsheets</em></link>
and template files included by means of XInclude.
</p>
@@ -424,7 +422,7 @@
If found, it's loaded in a language-specific way and then returned to
the calling environment.
Failing that, the source file is located and the language-specific
- <jump anchor="compiler">compiler</jump> is invoked prior to actual
+ <link href="#compiler">compiler</link> is invoked prior to actual
program loading.
</p>
@@ -441,8 +439,8 @@
"outdated" as explained below) the language processor may need to
perform cleanup actions, such as releasing memory or (in the case
of Java-like compiled languages)
- <jump anchor="class-loader-reinstantiation">
- reinstantiating the class loader</jump>.
+ <link href="#class-loader-reinstantiation">
+ reinstantiating the class loader</link>.
</p>
<p>
@@ -493,7 +491,7 @@
<p>
Compiled programs use a language-specified
- <jump anchor="class-loader">class loader</jump> to create
+ <link href="#class-loader">class loader</link> to create
a new program instance.
</p>
@@ -593,7 +591,7 @@
<ul>
<li>Variable <code>compilerClass</code>. Used to create instances
of the language's
- <jump anchor="compiler">compiler</jump>.
+ <link href="#compiler">compiler</link>.
</li>
<li>Variable <code>deleteSources</code>. Used to state whether
intermediate source files should be deleted after successful
@@ -790,7 +788,7 @@
For Java-based compiled languages (i.e., those using
<em>class files</em> as their object format, unloading implies
reinstantiating their
- <jump anchor="class-loader">class loader</jump>
+ <link href="#class-loader">class loader</link>
such that it "forgets" about previously loaded classes thus
becoming able to refresh class files updates since their last
load.
@@ -1159,9 +1157,9 @@
<p>
Named logicsheets are used as
- <jump anchor="builtin-logicsheets">
+ <link href="#builtin-logicsheets">
builtin logicsheets
- </jump>
+ </link>
by <code>AbstractMarkupLanguage</code>
to preload logicsheets and make them accessible
to dynamic XML documents without explicit declaration.
@@ -1555,7 +1553,7 @@
<p>
Method <code>load</code> uses its <code>markupLanguageName</code> and
<code>programmingLanguage</code> arguments to retrieve the corresponding
- <jump anchor="named-components"><code>NamedComponent</code></jump>
+ <link href="#named-components"><code>NamedComponent</code></link>
instances.
</p>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
