You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by st...@locus.apache.org on 2000/01/18 17:57:16 UTC
cvs commit: xml-site/sources/cocoon changes-sbk.xml cocoon2-sbk.xml dcpprocessor-sbk.xml dynamic-sbk.xml faq-sbk.xml guide-sbk.xml index-sbk.xml installing-sbk.xml javadoc-sbk.xml license-sbk.xml sqlprocessor-sbk.xml technologies-sbk.xml todo-sbk.xml WD-xsp-sbk.xml
stefano 00/01/18 08:57:16
Modified: sources/cocoon changes-sbk.xml cocoon2-sbk.xml
dcpprocessor-sbk.xml dynamic-sbk.xml faq-sbk.xml
guide-sbk.xml index-sbk.xml installing-sbk.xml
javadoc-sbk.xml license-sbk.xml
sqlprocessor-sbk.xml technologies-sbk.xml
todo-sbk.xml WD-xsp-sbk.xml
Log:
updated
Revision Changes Path
1.4 +301 -240 xml-site/sources/cocoon/changes-sbk.xml
Index: changes-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/changes-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- changes-sbk.xml 1999/12/16 01:36:17 1.3
+++ changes-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,419 +1,480 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Changes"><s2 title="Main Developers"><ul><li><anchor name="SM"/><jump href="mailto:stefano@apache.org">Stefano Mazzocchi</jump></li><li><anchor name="DB"/><jump href="mailto:balld@webslingerZ.com">Donald Ball</jump></li><li><anchor name="RR"/><jump href="mailto:rrocha@plenix.org">Ricardo Rocha</jump></li></ul></s2>
+<s1 title="Changes"><s2 title="Main Developers"><ul><li><anchor name="SM"/><jump href="mailto:stefano@apache.org">Stefano Mazzocchi</jump></li><li><anchor name="DB"/><jump href="mailto:balld@webslingerZ.com">Donald Ball</jump></li><li><anchor name="RR"/><jump href="mailto:rrocha@apache.org">Ricardo Rocha</jump></li></ul></s2>
- <s2 title="Cocoon 1.6-dev (not yet released)"><ul>
- <li><img alt="add" src="images/add.jpg"/>
+ <s2 title="Cocoon 1.6-dev (not yet released)"><ul>
+ <li><img alt="update" src="images/update.jpg"/>
+ Fixed command line operation.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
+ Cleaned up XSLTProcessor code.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
+ Added samples about external entities and XSLT import.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
+ Fixed ability to include/import from stylesheets.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
+ Fixed ability to include external entities with relative paths.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
+ Fixed Servlet API illegal state when setting the content type after acquiring the
+ servlet response instance.
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:axel.mueller@i2c-systems.com">Axel M\u00fcller</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
+ Added XSP sample pages.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
+ Cleaned-up docs, in preparation for release.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
+ Tuned Xerces attributes for speed.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
+ Added VRML formatter.
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:jmbirchfield@proteus-technologies.com">James Birchfield</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
+ Updated XSP working draft to match implementation (the WD was slowly changed
+ during development to match new emerging needs).
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
+ Added XSP primer in documentation.
+ (<jump href="#RR">RR</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
+ Added implementation of the XSP technology. The Cocoon Project is thankful to
+ <jump href="http://www.exoffice.com">Exoffice Technologies</jump> that sponsored
+ the creation of such implementation by hiring Ricardo and donated it to the project.
+ (<jump href="#RR">RR</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
+ Added examples on how to call the Cocoon engine from another servlet.
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:bmclaugh@algx.net">Brett McLaughlin</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
+ Added better documentation in the build.xml file for how to build Cocoon.
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
+ Added LDAP processor documentation.
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:jmbirchfield@proteus-technologies.com">James Birchfield</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
+ Added the singleton pattern to Engine to allow use of Cocoon from Turbine.
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:bmclaugh@algx.net">Brett McLaughlin</jump>.</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
+ Fixed language and typos in technology.xml.
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:raw@raw.com">Richard A. Wells</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
+ Added LDAP processor and samples.
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:jmbirchfield@proteus-technologies.com">James Birchfield</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Made ServletResponse and ServletContext available to engine and processors. This will require
further abstraction to avoid processors from messing up with the response output stream.
- (<jump href="#RR">RR</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#RR">RR</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed DCP problems on getting property file when cocoon.jar is in classpath under java 1.1 JVMs.
- (<jump href="#RR">RR</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#RR">RR</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the ability to return HTTP error messages from Cocoon.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Added dummy methods to EngineWrapper for JSDK 2.2 compatibility
- (<jump href="#DB">DB</jump>) Thanks to <jump href="mailto:martinguitar@hotmail.com">Brett McLaughlin</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#DB">DB</jump>) Thanks to <jump href="mailto:bmclaugh@algx.net">Brett McLaughlin</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added ProducerFromMap as a sitemap primer.
- (<jump href="#DB">DB</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#DB">DB</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added Tomcat installation instructions.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:bmclaugh@algx.net">Brett McLaughlin</jump>.</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:bmclaugh@algx.net">Brett McLaughlin</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
Moved a few things around in ColumnFormatter so that it's possible for columns to be formatted as more than simply a text node (e.g. embedded HTML). Also added a little formatter that can transform \n into <br> for text and varchar columns.
- (<jump href="#DB">DB</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#DB">DB</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added new classes to SQLProcessor to do column-specific date formatting.
- (<jump href="#DB">DB</jump>) Thanks to <jump href="mailto:ed@waterfall.freeserve.co.uk">Ed Ward</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#DB">DB</jump>) Thanks to <jump href="mailto:ed@waterfall.freeserve.co.uk">Ed Ward</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Add new producer for POST document processing, also useful for use of
Cocoon as a module (see EngineWrapper).
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:grit@wwcn.org">Gerrit Hiddink</jump>.</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:grit@wwcn.org">Gerrit Hiddink</jump>.</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed null problem in MemoryStore for command line operation.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ambarish.chaudhari@ecapsol.com">Ambarish Chaudhari</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ambarish.chaudhari@ecapsol.com">Ambarish Chaudhari</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added Ant build file.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added Documentation DTD.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Moved "examples/" under "samples/" for global xml.apache.org pattern.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Removed the makefile and moved to Ant as building system.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Moved all documentation and util files (todo, changes) to XML.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated support for Sun ProjectX TR2.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated the parser interface to allow better entity evaluation. :)
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added Xerces and Xalan support which now become the default components (finally!). :)
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed XML4j and LotusXSL support.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed support for Oracle products since it was too difficult to maintain it due to
requirement that Oracle XSLT processor worked on Oracle own DOM implementation.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added VoiceML sample file.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ted@groupserve.com">Ted Achacoso</jump>.</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ted@groupserve.com">Ted Achacoso</jump>.</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed all old PI formats from docs and properties file.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:simon@balr.com">Simon McClenahan</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:simon@balr.com">Simon McClenahan</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added a public method to FormatterFactory to allow more direct formatting.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:zvia@netmanage.co.il">Zvi Avraham</jump>.</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:zvia@netmanage.co.il">Zvi Avraham</jump>.</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Patched EngineWrapper to allow FileProducer to work when called from command line.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:hiddinkg@cs.utwente.nl">Gerrit Hiddink</jump>.</li>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:hiddinkg@cs.utwente.nl">Gerrit Hiddink</jump>.</li>
</ul></s2>
-<s2 title="Cocoon 1.5 (October 29 1999)"><ul>
- <li><img alt="fix" src="images/fix.jpg"/>
+<s2 title="Cocoon 1.5 (October 29 1999)"><ul>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed concurrency problem in XML4j parser.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:harris@columbus.rr.com">Jeffrey Thomas Harris</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:harris@columbus.rr.com">Jeffrey Thomas Harris</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added JRun installation instructions.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:sstirlin@gis.net">Scott Stirling</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:sstirlin@gis.net">Scott Stirling</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added more info on the Cocoon status page.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:dlehn@vt.edu">David Lehn</jump>.</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:dlehn@vt.edu">David Lehn</jump>.</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Patched OpenXML that had a bug in the XML publisher that didn't support doctypes imposed from the
outside. This was breaking the WML formatter.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Patched XSL:P to support <xsl:processing-instruction> instead of <xsl:pi> which is now deprecated.
This makes XSL:P a hybrid between XSLT revisions but it's easier this way than to create two sets
of examples that work with latest and oldest releases of XSLT. Hopefully XSLT will standardize soon.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed XML4J support bug.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:harris@columbus.rr.com">Jeffrey Thomas Harris</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:harris@columbus.rr.com">Jeffrey Thomas Harris</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added XSL:P Formatters.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated XSL:P to build 19991017.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added parameter visibility to formatters to allow request-dependent formatting.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ben@algroup.co.uk">Ben Laurie</jump>.</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ben@algroup.co.uk">Ben Laurie</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
Changed Hashtable in more abstract Dictionary in all interfaces (this will
be updated to collection classes when JDK 1.2 is available).
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated Fop to version 0.11
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added a work-around for the JServ1.1b2 bug.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:malimpen@dei.unipd.it">Stefano Malimpensa</jump>.</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:malimpen@dei.unipd.it">Stefano Malimpensa</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated documentation.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the plan for JavaDOC XML generator and the JavaDOC DTD working draft.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:murphyk@umsystem.edu">Kenneth Murphy</jump>.</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:murphyk@umsystem.edu">Kenneth Murphy</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated examples, especially the WML example which was based on an obsolete WML DTD.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added WML formatter.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the ability to "mount" the Cocoon status to a configurable URL.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the ability to hide Cocoon status for security reasons.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed the persistent part of the object store since it's not used.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed DCP problem in loading the initScript.es file as system resource.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added some better diagnostic hooks.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ben@algroup.co.uk">Ben Laurie</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ben@algroup.co.uk">Ben Laurie</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added SQLProcessor.
- (<jump href="#DB">DB</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#DB">DB</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed a bug in the EcmaScript language interpreter.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:malimpen@dei.unipd.it">Stefano Malimpensa</jump>.</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:malimpen@dei.unipd.it">Stefano Malimpensa</jump>.</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed problems on startup without complete configurations and written more
descriptive error messages on exceptions.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated the examples to reflect the changes.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Changed Cocoon illegal PIs from <?cocon:xxx?> to <?cocoon-xxx?>.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:tbray@textuality.com">Tim Bray</jump>.</li>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:tbray@textuality.com">Tim Bray</jump>.</li>
</ul></s2>
-<s2 title="Cocoon 1.4 (September 13 1999)"><ul>
- <li><img alt="fix" src="images/fix.jpg"/>
+<s2 title="Cocoon 1.4 (September 13 1999)"><ul>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed portability issues with JRun and Sun's JSWDK.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:hannes@haug.com">Hannes Haug</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:hannes@haug.com">Hannes Haug</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added parsed stylesheets caching capabilities to the AbstractXSLTProcessor:
now if produced files are changed but stylesheets don't, the second are not
reparsed, improving the system performance since this is a very frequent
case.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Reduced the memory footprint of some classes by initializing the
hashtables to lower values than default.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Improved the speed of PI searching by looking for first found PI instead
of scanning the whole file.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated the cocoon processing instructions that drive the reaction: <?cocoon:process?>
drives the processing reaction, <?cocoon.format?> indicates the
formatter used to end processing and format the document.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed the processor pipeline and replaced with a reactor-type router
with PI-based reaction.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Moved the example classes in their own package for easier installation and testing.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Modified a number of classes to fit the new Store and Cache subframeworks.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added a first implementation of the Cache interface based on dynamic
evaluation of changeable points.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added a first implementation of the Store interface based on serialization
persistency wrapped by an adaptively managed memory buffer.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added support for the Oracle XSL Processor (works only with the Oracle XML Parser).
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the Store framework.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Included FOP Version 0.9.1 that partially supports latest XSL Formatting
Object specification (19990421).
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:jtauber@jtauber.com">James Tauber</jump>.</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:jtauber@jtauber.com">James Tauber</jump>.</li>
+ <li><img alt="update" src="images/update.jpg"/>
Included XSL:P Version 1.0 Beta (19990823) that supports latest XSLT
specification (19990421).
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:kvisco@ziplink.net">Keith Visco</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:kvisco@ziplink.net">Keith Visco</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Introduced the Actor/Director concept to allow cleaner implementation and
configuration of dynamically loaded objects.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the WAP example to show how Cocoon can serve the same content to fat
HTML clients and thin WML clients such as WAP-enabled cellular phones or PDA.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed the need for a properties file in DCP.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed a minor bug in Configurations.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:hannes@haug.com">Hannes Haug</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:hannes@haug.com">Hannes Haug</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the Producer subframework for easier dynamic XML generation.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Rewritten and cleaned up the formatting section using the Router abstract class.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Rewritten some of the underlying design pattern implementations.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed bug in SunXMLParser not implementing Status.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:chris_conway@mail.scp.com">Christopher Conway</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:chris_conway@mail.scp.com">Christopher Conway</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added support for Oracle XML parser.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:chris_conway@mail.scp.com">Christopher Conway</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:chris_conway@mail.scp.com">Christopher Conway</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added Dynamic Content Processor.
- (<jump href="#RR">RR</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#RR">RR</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Updated sample configurations to reflect the changes.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Rewritten the PI parser for more general use in AbstractXSLProcessor.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Created the EngineWrapper class to extend the Engine class for use on
non-servlet based applications.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the possibility to use request parameters to trigger special events
on the page. Currently debug and cache are supported.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added request and cache as parameters for the processor chain as requested
by more sophisticated processors.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Changed the cache system interface to match new needs.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Changed the printing architecture. Now, you don't need to specify the type
of formattation but the publishing system will understand it for you (based
on processing instructions and the specified document type).
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added white paper on the Cocoon 2 architecture for public review.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed typos, added support for more detailed verbosity and fixed a
path-parsing bug for win32 systems.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:paul_ororke@sparks.com">Paul O'Rorke</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:paul_ororke@sparks.com">Paul O'Rorke</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added support for James Tauber's FOP to translate XSL:FO-styled documents
into PDF documents.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:jtauber@jtauber.com">James Tauber</jump>.</li>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:jtauber@jtauber.com">James Tauber</jump>.</li>
</ul></s2>
-<s2 title="Cocoon 1.3.1 (May 31 1999)"><ul>
- <li><img alt="add" src="images/add.jpg"/>
+<s2 title="Cocoon 1.3.1 (May 31 1999)"><ul>
+ <li><img alt="add" src="images/add.jpg"/>
Added the first finished working draft of the XSP specification for public review.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed the XML and XSL specifications from the distribution.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed a deadlock problem in the cache system.
- (<jump href="#DB">DB</jump>)</li>
+ (<jump href="#DB">DB</jump>)</li>
</ul></s2>
-<s2 title="Cocoon 1.3 (May 12 1999)"><ul>
- <li><img alt="add" src="images/add.jpg"/>
+<s2 title="Cocoon 1.3 (May 12 1999)"><ul>
+ <li><img alt="add" src="images/add.jpg"/>
Included more detailed example of future XSP technology.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Patched the Sun ProjectX parser wrapper to work with latest release. Added also a Sun printer class.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:shecter@darmstadt.gmd.de">Robb Shecter</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:shecter@darmstadt.gmd.de">Robb Shecter</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the ability to call Cocoon from the command line.
- (<jump href="#DB">DB</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#DB">DB</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed the final Vector.toString() problem in JDK 1.1 compilation.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed the "verify error" by using Jikes compiler for distribution.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Cleaned up documentation and added some entries in the FAQ.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed win32 batch scripts and rewritten the makefile.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added a better cache engine.
- (<jump href="#DB">DB</jump>)</li>
+ (<jump href="#DB">DB</jump>)</li>
</ul></s2>
-<s2 title="Cocoon 1.2 (April 30 1999)"><ul>
- <li><img alt="update" src="images/update.jpg"/>
+<s2 title="Cocoon 1.2 (April 30 1999)"><ul>
+ <li><img alt="update" src="images/update.jpg"/>
Improved documentation and cleaned things around.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Changed versions of both OpenXML and XSL:P.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Moved the core processing into a different class named Engine, first step
to a complete servlet/application duality.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the Cocoon status handler.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added a better user interface for the servlet and a nicer look to report errors.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added the OpenXML printer wrapper class that uses the new X3P API.
- (<jump href="#DB">DB</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#DB">DB</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Changed the initialization section to match exceptions thrown on different
servlet platforms.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Changed behavior to identity transformation through the DOM processors if
no PI are found.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:george@moberg.com">George T. Talbot</jump>.</li>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:george@moberg.com">George T. Talbot</jump>.</li>
</ul></s2>
-<s2 title="Cocoon 1.1.1 (Apr 5 1999)"><ul>
- <li><img alt="fix" src="images/fix.jpg"/>
+<s2 title="Cocoon 1.1.1 (Apr 5 1999)"><ul>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed a problem with the getClassloader() method returning null. Now
Cocoon doesn't always use the internal properties file but adds hardcoded
default values. This is because in Java 1.1 there is no getSystemClassloader()
method.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Included the updated versions of both OpenXML 1.0.5 and XSL:P 19990326
which should fix lots of bugs and improve the overall performance.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Patched to avoid the use of File.toURL() method which is not found under
the Java1 platform.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:adrian_durkin@hotmail.com">Adrian Durkin</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:adrian_durkin@hotmail.com">Adrian Durkin</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added DoNothingCache to avoid caching during document debugging.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ritter@wt.net">Greg Ritter</jump>.</li>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ritter@wt.net">Greg Ritter</jump>.</li>
</ul></s2>
-<s2 title="Cocoon 1.1 (March 25 1999)"><ul>
- <li><img alt="update" src="images/update.jpg"/>
+<s2 title="Cocoon 1.1 (March 25 1999)"><ul>
+ <li><img alt="update" src="images/update.jpg"/>
Changed the stylesheet mapping processing instruction from illegal "xml:stylesheet"
to standard "xml-stylesheet".
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Created Cocoon logo.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added LRU caching (both memory and disk).
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ritter@wt.net">Greg Ritter</jump>.</li>
- <li><img alt="add" src="images/add.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:ritter@wt.net">Greg Ritter</jump>.</li>
+ <li><img alt="add" src="images/add.jpg"/>
Added support for XSL:P processor.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:kvisco@ziplink.net">Keith Visco</jump>.</li>
- <li><img alt="remove" src="images/remove.jpg"/>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:kvisco@ziplink.net">Keith Visco</jump>.</li>
+ <li><img alt="remove" src="images/remove.jpg"/>
Removed support for Koala XSL parser.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="update" src="images/update.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="update" src="images/update.jpg"/>
Redesigned internal framework.
- (<jump href="#SM">SM</jump>)</li>
- <li><img alt="fix" src="images/fix.jpg"/>
+ (<jump href="#SM">SM</jump>)</li>
+ <li><img alt="fix" src="images/fix.jpg"/>
Fixed some typos and English bugs in docs.
- (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:patrick@cre8tivegroup.com">Patrick Gardella</jump>.</li>
+ (<jump href="#SM">SM</jump>) Thanks to <jump href="mailto:patrick@cre8tivegroup.com">Patrick Gardella</jump>.</li>
</ul></s2>
-<s2 title="Cocoon 1.0 (March 10 1999)"><ul>
- <li><img alt="add" src="images/add.jpg"/>
+<s2 title="Cocoon 1.0 (March 10 1999)"><ul>
+ <li><img alt="add" src="images/add.jpg"/>
Initial version.
- (<jump href="#SM">SM</jump>)</li>
+ (<jump href="#SM">SM</jump>)</li>
</ul></s2>
</s1>
1.4 +9 -9 xml-site/sources/cocoon/cocoon2-sbk.xml
Index: cocoon2-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/cocoon2-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- cocoon2-sbk.xml 1999/12/16 01:36:17 1.3
+++ cocoon2-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Cocoon 2">
+<s1 title="Cocoon 2">
- <s2 title="Introduction">
+ <s2 title="Introduction">
<p>The Cocoon Project has gone a long way since it's creation on
January 1999. It started as a simple servlet for static XSL styling and became
more and more powerful as new features were added. Unfortunately, design
@@ -24,7 +24,7 @@
be a winner, especially if based on open standards.</p>
</s2>
- <s2 title="Passive APIs vs. Active APIs">
+ <s2 title="Passive APIs vs. Active APIs">
<p>Web serving environments must be fast and scalable to be
useful. Cocoon1 was born as a "proof of concept" rather than a
production software and had significant design restrictions based mainly on
@@ -110,7 +110,7 @@
component projects to be able to influence their operation in this direction.</p>
</s2>
-<s2 title="Reactors Reconsidered">
+<s2 title="Reactors Reconsidered">
<p>Another design choice that should be revised is the reactor
pattern that was introduced to allow components to be connected in more
flexible way. In fact, opposed to the fixed pipe model used up to Cocoon
@@ -127,7 +127,7 @@
remains: there is no single point of management.</p>
</s2>
-<s2 title="Management Considerations">
+<s2 title="Management Considerations">
<p>The web was created to reduce information management costs by
distributing them back on information owners. While this model is great for
user communities (scientists, students, employees, or people in general) each
@@ -159,7 +159,7 @@
<p>The model that Cocoon2 adopts is the "pyramid model of
web contracts" which is outlined in the picture below</p>
- <p><img alt="The Cocoon2 Pyramid Model of Contracts" src="images/pyramid-model.gif"/></p>
+ <p><img alt="The Cocoon2 Pyramid Model of Contracts" src="images/pyramid-model.gif"/></p>
<p>and is composed by four different working contexts (the rectangles)</p>
@@ -198,7 +198,7 @@
</ul>
</s2>
-<s2 title="Overlapping contexts and Chain Mapping">
+<s2 title="Overlapping contexts and Chain Mapping">
<p>The above model can be applied only if the different contexts
never overlap, otherwise there is no chance of having a single management
point. For example, if the W3C-recommended method to link stylesheets to XML
@@ -230,7 +230,7 @@
request-time interpretation solutions like DCP that will be removed.</p>
</s2>
-<s2 title="Pre-compilation, Pre-generation and Caching">
+<s2 title="Pre-compilation, Pre-generation and Caching">
<p>The cache system in Cocoon1 will be ported with no important
design changes since it's very flexible and was not polluted by early design
constraints since it appeared in later versions. The issue regards static file
@@ -258,7 +258,7 @@
hooks that will work like normal compilers from a developer's point of view.</p>
</s2>
-<s2 title="Conclusions">
+<s2 title="Conclusions">
<p>Cocoon2 is a big and very ambitious project, not only for the
technological issues involved (which will require strong integration with XML
components) but also for the significant paradigm shifts imposed by the new
1.4 +26 -26 xml-site/sources/cocoon/dcpprocessor-sbk.xml
Index: dcpprocessor-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/dcpprocessor-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- dcpprocessor-sbk.xml 1999/12/16 01:36:17 1.3
+++ dcpprocessor-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="DCPProcessor User Guide">
+<s1 title="DCP Processor">
- <s2 title="Introduction">
+ <s2 title="Introduction">
<p>
In addition to static content (that is, hand-written documents produced
by web authors), web publishing also requires <ref>dynamic content
@@ -21,12 +21,12 @@
</p>
</s2>
- <s2 title="Origins">
+ <s2 title="Origins">
<p>
The Cocoon community has long recognized the need for dynamic content
generation capabilities. In response to this requirement, the Cocoon
project has proposed
- <jump href="http://xml.apache.org/cocoon/xsp.html">XSP</jump>
+ <jump href="http://xml.apache.org/cocoon/xsp.html">XSP</jump>
(<ref>eXtensible Server Pages</ref>). XSP defines a new XML DTD and
namespace that addresses a complete region of web publishing, that of
logic-based, dynamic content generation. XSP is a key component of future
@@ -43,7 +43,7 @@
</p>
</s2>
- <s2 title="Goals">
+ <s2 title="Goals">
<p>
DCP has been designed to provide dynamic content generation capabilities
to Cocoon with the following goals in mind:
@@ -112,13 +112,13 @@
<p>
Jean-Marc Lugrin's
- (<jump href="http://home.worldcom.ch/jmlugrin/fesi/index.html">Fesi</jump>)
+ (<jump href="http://home.worldcom.ch/jmlugrin/fesi/index.html">Fesi</jump>)
(<ref>Free EcmaScript Interpreter</ref>) is used to provide support for
Javascript.
</p>
</s2>
- <s2 title="Relationship with Existing Technologies">
+ <s2 title="Relationship with Existing Technologies">
<p>
DCP (and XSP, for that matter) differs from existing dynamic web content
generation technologies in that it deals with DOM trees rather than with
@@ -133,24 +133,24 @@
</p>
<p>
- <jump href="http://www.javasoft.com/products/jsp/index.html">JSP</jump>,
+ <jump href="http://www.javasoft.com/products/jsp/index.html">JSP</jump>,
in particular, is a widely used standard in the Java environment. Other
comparable technologies are Microsoft's
- <jump href="http://www.microsoft.com/ntserver/web/deployment/planguide/WebAppDev.asp">
+ <jump href="http://www.microsoft.com/ntserver/web/deployment/planguide/WebAppDev.asp">
ASP
</jump>,
- <jump href="http://www.coldfusion.com/">
+ <jump href="http://www.coldfusion.com/">
Cold Fusion
</jump>,
Sun's [deprecated]
- <jump href="http://www.sun.com/software/jwebserver/features/index.html#dsp">
+ <jump href="http://www.sun.com/software/jwebserver/features/index.html#dsp">
Page Compilation
</jump>,
- <jump href="http://www.webmacro.org/">
+ <jump href="http://www.webmacro.org/">
Webmacro
</jump>
and
- <jump href="http://www.bitmechanic.com/projects/gsp">
+ <jump href="http://www.bitmechanic.com/projects/gsp">
GSP
</jump>.
</p>
@@ -199,13 +199,13 @@
</p>
</s2>
- <s2 title="A Simple Javascript Example">
+ <s2 title="A Simple Javascript Example">
<p>
Consider the following dynamic Cocoon XML document
- (<jump href="http://www.plenix.com/dcp/ecmascript/sample.xml?country=Canada&language=English&language=French">sample.xml</jump>):
+ (<jump href="http://www.plenix.com/dcp/ecmascript/sample-page.xml?country=Canada&language=English&language=French">sample.xml</jump>):
</p>
- <p><img alt="Ecmascript Example" src="images/dcp-fig-1.gif"/></p>
+ <p><img alt="Ecmascript Example" src="images/dcp-fig-1.gif"/></p>
<p>
In this example, portions shown in red are to be dynamically generated
@@ -367,7 +367,7 @@
That said, the source XML document for the above example would be:
</p>
- <p><img alt="Ecmascript Example Source" src="images/dcp-fig-2.gif"/></p>
+ <p><img alt="Ecmascript Example Source" src="images/dcp-fig-2.gif"/></p>
<p>
In this document:
@@ -617,7 +617,7 @@
<li>
<code>connectionName</code>.
A connection pool name as specified by Gefion Software's
- <jump href="http://www.webdevelopersjournal.com/columns/connection_pool.html">
+ <jump href="http://www.webdevelopersjournal.com/columns/connection_pool.html">
<code>DBConnectionManager</code>
</jump>
in the resource file
@@ -720,7 +720,7 @@
</s2>
- <s2 title="Java DCP Programming">
+ <s2 title="Java DCP Programming">
<p>
For the Java language, the attribute <code>code</code> in the declaration
</p>
@@ -904,7 +904,7 @@
</source>
</s2>
- <s2 title="Known Problems">
+ <s2 title="Known Problems">
<ul>
<li>
<em>Restricted Static Parameter Passing</em>.
@@ -945,7 +945,7 @@
<br/><br/>
An alternative would be the use of Netscape's
- <jump href="http://www.mozilla.org/rhino/">Rhino</jump>
+ <jump href="http://www.mozilla.org/rhino/">Rhino</jump>
(which supports compilation to class files),
but this may create incompatibilities with existing programs
that depend on FESI features.
@@ -977,11 +977,11 @@
</ul>
</s2>
- <s2 title="Additional Examples">
+ <s2 title="Additional Examples">
<p>
In addition to the examples presented in this document, there is a more
complex application written entirely in Cocoon using Java DCP: the
- <jump href="http://www.plenix.com/translator/">
+ <jump href="http://www.plenix.com/translator/">
Cocoon Multilingual Dictionary
</jump>.
</p>
@@ -994,15 +994,15 @@
</p>
</s2>
- <s2 title="Future Directions">
+ <s2 title="Future Directions">
<p>
DCP will be deprecated in favor of
- <jump href="http://xml.apache.org/cocoon/xsp.html">XSP</jump>.
+ <jump href="http://xml.apache.org/cocoon/xsp.html">XSP</jump>.
Therefore, development is currently limited to bug fixes.
</p>
</s2>
- <s2 title="Acknowledgments">
+ <s2 title="Acknowledgments">
<p>
The following people have contributed to the definition of DCP:
</p>
1.4 +23 -23 xml-site/sources/cocoon/dynamic-sbk.xml
Index: dynamic-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/dynamic-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- dynamic-sbk.xml 1999/12/16 01:36:17 1.3
+++ dynamic-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Dynamic XML in Cocoon">
+<s1 title="Dynamic XML in Cocoon">
-<s2 title="Introduction">
+<s2 title="Introduction">
<p>Web publishing is very limited without the ability to create
dynamic content. For dynamic XML we refer to the content that is created as a
function of request parameters or state of the requested resource. For this
@@ -11,7 +11,7 @@
content to be generated.</p>
</s2>
-<s2 title="The Servlet/JSP model">
+<s2 title="The Servlet/JSP model">
<p>People are used to write small Java programs to create their
dynamic web content. Servlets, and Java in general, are very powerful, easy to
write and fast to debug, but they impose (like any other pure-logic solution)
@@ -34,7 +34,7 @@
isn't so.</p>
</s2>
-<s2 title="Servlet Chaining Vs. Servlet Nesting">
+<s2 title="Servlet Chaining Vs. Servlet Nesting">
<p>Java Servlets were introduced by the Java Web Server team as a
way to allow users to create their own <ref>web plug-ins</ref>. They were designed
to handle the HTTP protocol and all possible dynamic web content (including
@@ -55,7 +55,7 @@
the need for servlet chaining</p>
</s2>
-<s2 title="The limitations of Servlet Nesting">
+<s2 title="The limitations of Servlet Nesting">
<p>While servlet nesting was a major advantage over servlet
chaining because it allowed servlets to be somewhat modular without loosing
the full API power, a common design pattern applies to the Servlet model in
@@ -72,7 +72,7 @@
Piping</ref>.</p>
</s2>
-<s2 title="The Cocoon model">
+<s2 title="The Cocoon model">
<p>Rather than turning Cocoon into a servlet engine, thus
limiting its portability, this documents outlines some solutions that allow
Cocoon users to get the servlet-equivalent functionality with internal Cocoon
@@ -96,7 +96,7 @@
your own to fit your particular needs.</p>
</s2>
-<s2 title="Writing Producers">
+<s2 title="Writing Producers">
<p>Producers initiate the request handling phase. They are
responsible to evaluate the HttpServletRequest parameters provided and create
XML content that is fed into the processing reactor. A servlet logic should be
@@ -150,7 +150,7 @@
use your own producers.</p>
</s2>
-<s2 title="Writing Processors">
+<s2 title="Writing Processors">
<p>If your servlet needs many parameters to work, it is more
reasonable that you write a Processor instead. A Processor transforms a given
XML document (which, in this case should contain the needed static parameters)
@@ -184,7 +184,7 @@
use your own processors.</p>
</s2>
-<s2 title="Using Cocoon processors">
+<s2 title="Using Cocoon processors">
<p>The above example shows a very simple situation but needs
non-trivial code to implement it. For this reason, the Cocoon distribution
includes a number of processors that implement common needs and situations.
@@ -198,6 +198,13 @@
its extensible and programmable nature.
</li>
+ <li><em>The XSP processor</em> -
+ the XSP processor that evaluates XSP pages and compiles them into
+ producers. This processor allows you include programmatic logic into
+ your pages as well as to separate the logic from the content. See the
+ XSP user guide for more information.
+ </li>
+
<li><em>The DCP processor</em> -
the DCP processor that evaluates XML processing
instructions with multi-language (Java and EcmaScript) logic. This
@@ -213,20 +220,13 @@
processor user guide for more information.
</li>
+ <li><em>The LDAP processor</em> -
+ the LDAP processor that evaluates simple tags
+ describing LDAP queries to directory services and formats their result-set in XML
+ depending on given parameters. See the LDAP
+ processor user guide for more information.
+ </li>
+
</ul>
-</s2>
-
-<s2 title="Future plans">
- <p>While the above represents a complete set of usable components
- for dynamic XML content generation, the Cocoon project aims to separate all
- three layers (content, logic and style). While XSLT transformations allow a
- perfect separation between content and style with the use of stylesheets, the
- separation between content and logic in dynamically generated XML pages is not
- achieved with current Cocoon features.</p>
-
- <p>To fill this whole, the XSP
- (eXtensible Server Pages) technology was proposed. While in the <ref>working
- draft</ref> stage, we strongly believe that some of the issues expressed in that
- specification will be keys to the future of dynamic XML.</p>
</s2>
</s1>
1.4 +166 -28 xml-site/sources/cocoon/faq-sbk.xml
Index: faq-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/faq-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq-sbk.xml 1999/12/16 01:36:17 1.3
+++ faq-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,11 +1,30 @@
<?xml version="1.0" encoding="UTF-8"?>
<faqs>
-<faq title="How do I pipe my servlet output into Cocoon?">
+<faq title="Previous Cocoon releases said that this product was to consider a proof of concept rather than a working solution. I can't find that sentence anymore. What happened?">
+ <q>Previous Cocoon releases said that this product was to consider a
+ proof of concept rather than a working solution. I can't find that sentence
+ anymore. What happened?</q>
+ <a>
+ <p>We believe that Cocoon has entered the final stage of its evolution but
+ as it stands today, it is ready to be used for a production environment.</p>
+ <p>Careful, we don't say it's perfect or bug-free, this is impossible to say,
+ but at least, we think this technology is good enough for you to try it out
+ against other solutions for web publishing.</p>
+ <p>Warning: this doesn't mean that Cocoon evolution came to an end, not at all,
+ but that we believe it's mature enough to be deployed in a working environment
+ with no particular problems.</p>
+ <p>Note, however, that this software comes "as is" so you should always be
+ aware of the risks as for any other open source software, but I think that
+ if you read this, you already know what we mean :)</p>
+ </a>
+</faq>
+
+<faq title="How do I pipe my servlet output into Cocoon?">
<q>How do I pipe my servlet output into Cocoon?</q>
<a>
- <p>Simple answer: <ref>you don't!!!</ref> read this
- document instead to find out equivalent ways to do what you need.</p>
+ <p>Simple answer: <ref>you don't!!!</ref> read the page
+ about dynamic content to find out equivalent ways to do what you need.</p>
<p>Complex answer: the Servlet API <ref>was not</ref> designed with servlet
chaining capabilities in mind. Servlet chaining was a night hack of the
original Java web server authors that allowed to pipe one servlet output
@@ -22,7 +41,7 @@
</a>
</faq>
-<faq title="Where do I get more information on XSL and XML?">
+<faq title="Where do I get more information on XSL and XML?">
<q>Where do I get more information on XSL and XML?</q>
<a>
<p>
@@ -31,33 +50,129 @@
locations you might be interested in to continue to gather resources on this
state-of-the-art technology</p>
<ul>
- <li><jump href="http://www.xml.org">http://www.xml.org</jump> - A very nice site for XML
+ <li><jump href="http://www.xml.org">http://www.xml.org</jump> - A very nice site for XML
information.</li>
- <li><jump href="http://www.w3.org/markup/xml/">http://www.w3.org/markup/xml/</jump> - The XML
+ <li><jump href="http://www.w3.org/xml/">http://www.w3.org/xml/</jump> - The XML
official home page at W3C</li>
- <li><jump href="http://www.w3.org/style/xsl">http://www.w3.org/style/xsl</jump> - The XSL official
+ <li><jump href="http://www.w3.org/style/xsl">http://www.w3.org/style/xsl</jump> - The XSL official
home page W3C</li>
- <li><jump href="http://www.software.ibm.com/xml/education/tutorial-prog/abstract.html">http://www.software.ibm.com/xml/education/tutorial-prog/abstract.html</jump>
+ <li><jump href="http://www.software.ibm.com/xml/education/tutorial-prog/abstract.html">http://www.software.ibm.com/xml/education/tutorial-prog/abstract.html</jump>
- XML Tutorial from IBM</li>
- <li><jump href="http://www.webtechniques.com/features/1999/01/walsh/walsh.shtml">http://www.webtechniques.com/features/1999/01/walsh/walsh.shtml</jump>
+ <li><jump href="http://www.webtechniques.com/features/1999/01/walsh/walsh.shtml">http://www.webtechniques.com/features/1999/01/walsh/walsh.shtml</jump>
- XSL Tutorial</li>
- <li><jump href="http://www.oasis-open.org/cover/xml.html">http://www.oasis-open.org/cover/xml.html</jump>
+ <li><jump href="http://www.oasis-open.org/cover/xml.html">http://www.oasis-open.org/cover/xml.html</jump>
- XML Resource Listing</li>
- <li><jump href="http://www.oasis-open.org/cover/xsl.html">http://www.oasis-open.org/cover/xsl.html</jump>
+ <li><jump href="http://www.oasis-open.org/cover/xsl.html">http://www.oasis-open.org/cover/xsl.html</jump>
- XSL Resource Listing</li>
- <li><jump href="http://www.xmlsoftware.com">http://www.xmlsoftware.com</jump> -
+ <li><jump href="http://www.xmlsoftware.com">http://www.xmlsoftware.com</jump> -
XML software listing</li>
- <li><jump href="http://www.xmlinfo.com">http://www.xmlinfo.com</jump> - XML
+ <li><jump href="http://www.xmlinfo.com">http://www.xmlinfo.com</jump> - XML
information updates on W3C status and others</li>
- <li><jump href="http://www.xslinfo.com">http://www.xslinfo.com</jump> - XSL
+ <li><jump href="http://www.xslinfo.com">http://www.xslinfo.com</jump> - XSL
information, updates, example stylesheets</li>
- <li><jump href="http://www.schema.net">http://www.schema.net</jump> - Repository
+ <li><jump href="http://www.schema.net">http://www.schema.net</jump> - Repository
of standard DTDs</li>
</ul>
</a>
</faq>
+
+<faq title="Are there document translations to other languages?">
+ <q>Are there document translations to other languages?</q>
+ <a>
+ <p>Given the problems we already have with documentation (which is never big and good enough),
+ the Cocoon Project uses English as its standard and only documentation language. This is also
+ the only language used in the mail lists. Also, the Cocoon distribution will contain
+ English documentation only to reduce updating problems.</p>
+ <p>On the other hand, we welcome any effort that provides document translations and
+ we will keep here links to those translated documents.</p>
+ <ul>
+ <li><jump href="http://www.epita.net">French Translation</jump></li>
+ </ul>
+ <note>The Cocoon Project is not directly involved in these translating efforts
+ and we are not resposible for any lack of synch between the official Cocoon
+ documentation and the translated version. For this reason, do not contact
+ the Cocoon Project but directly the people that provide the translation. Thank you.</note>
+ </a>
+</faq>
+
+<faq title="Why do I keep getting FileNotFoundException under Tomcat 3.0?">
+ <q>Why do I keep getting FileNotFoundException under Tomcat 3.0?</q>
+ <a>See question below</a>
+</faq>
+
+<faq title="How come Cocoon doesn't work on Tomcat 3.0?">
+ <q>How come Cocoon doesn't work on Tomcat 3.0?</q>
+ <a>
+ <p>You must apply this patch to Tomcat 3.0 and recompile it or it won't work.
+ This patch is already present in latest CVS code but in case you don't want
+ to download the latest code you can apply this:</p>
+
+ <source> Index: RequestMapper.java
+ ===================================================================
+ RCS file: /home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/core/RequestMapper.java,v
+
+ retrieving revision 1.5
+ retrieving revision 1.6
+ diff -u -r1.5 -r1.6
+ --- RequestMapper.java 1999/11/05 18:36:33 1.5
+ +++ RequestMapper.java 1999/12/17 18:59:14 1.6
+ @@ -285,13 +285,7 @@
+ mapPath = "/" + s;
+ } else if (mapPath == null &&
+ this.resourceName != null) {
+ - // XXX
+ - // hack to differentiate amongst a mapped servlet and a jsp
+ - if (! wrapper.getServletClass().equals(Constants.JSP.CLASSNAME)) {
+ - mapPath = "/" + wrapper.getServletClass();
+ - } else {
+ - mapPath = this.resourceName;
+ - }
+ + mapPath = this.resourceName;
+ }
+
+ return mapPath;</source>
+ </a>
+</faq>
+
+<faq title="Are external entities still broken?">
+ <q>Are external entities still broken?</q>
+ <a>
+ <p>No, external entity support has been fixed for both absolute and relative
+ URIs. Note that ProjectX and Xerces behave differently on these but this
+ is not something we are in control of.</p>
+ </a>
+</faq>
+
+<faq title="Why %lt;xsl:import%gt; and %lt;xsl:include%gt; don't work with Xalan?">
+ <q>Why %lt;xsl:import%gt; and %lt;xsl:include%gt; don't work with Xalan?</q>
+ <a>
+ <p>This is a problem in the way that Xalan handles DOM-based stylesheets, it will be
+ fixed as soon as Cocoon moves on a SAX based architecture. As a work around, you can
+ consider using XT which has no problems.</p>
+ </a>
+</faq>
+
+<faq title="I see that Cocon 1.x has starting to incorporate features planned for Cocoon 2.x, why?">
+ <q>I see that Cocon 1.x has starting to incorporate features planned for
+ Cocoon 2.x, why?</q>
+ <a>
+ <p>We believe that smooth project evolution is much better than step-wise
+ revolutionary paths. For this reason, we'll try hard to incorporate all the
+ Cocoon2 features in the main project thus limiting the porting effort for you
+ over time.</p>
+ <p>Note that this doesn't mean that Cocoon won't change in the future and we
+ state clearly that we do care about back compatibility but only when this is
+ not limiting the evolution of he platform too much.</p>
+ <p>For this reason, while the DOM->SAX evolution might be totally painless, the
+ sitemap proposal will completely change the Cocoon configurations. Anyway, Cocoon
+ has a long way to go and if it changes during its evolution to a final state,
+ don't complain: you have been warned.</p>
+ <p>However, we DO consider and value the time you invested in Cocoon so we'll
+ do our best to make sure that unneeded back incompatibilities don't get included.</p>
+ </a>
+</faq>
-<faq title="The XSL book I read says the correct way of indicating the XSL stylesheet is by     using the XML processing instruction <?xml:stylesheet?> while Cocoon is     using <?xml-stylesh
eet?>. Who is right?  ">
+<faq title="The XSL book I read says the correct way of indicating the XSL stylesheet is by using the XML processing instruction <?xml:stylesheet?> while Cocoon is using <?xml-stylesheet?>. Who is right? ">
<q>The XSL book I read says the correct way of indicating the XSL stylesheet is by
using the XML processing instruction <code><?xml:stylesheet?></code> while Cocoon is
using <code><?xml-stylesheet?></code>. Who is right?
@@ -69,12 +184,12 @@
discussing is not even in W3C Recommendation state. Which means that more changes are on
their way.</p>
<p>The current and proper way to associate a stylesheet with an XML document can be found at
- <jump href="http://www.w3.org/TR/xml-stylesheet">http://www.w3.org/TR/xml-stylesheet</jump> and
+ <jump href="http://www.w3.org/TR/xml-stylesheet">http://www.w3.org/TR/xml-stylesheet</jump> and
clearly indicates that <code><?xml-stylesheet ...?></code> is the proper way.</p>
</a>
</faq>
-<faq title="     I think that using Processing Instructions to "chain"     document layers somehow violates the context separation since I would like     to be able to place style sensible i
10;formation in sessions or request     parameters. What do you think about this?  ">
+<faq title=" I think that using Processing Instructions to "chain" document layers somehow violates the context separation since I would like to be able to place style sensible information in sessions or request parameters. What do you think about this? ">
<q>
I think that using Processing Instructions to "chain"
document layers somehow violates the context separation since I would like
@@ -88,7 +203,7 @@
processing chain for each requested URI and for every possible request state
(with request parameters, session parameters and environment parameters).</p>
<p>The proposed solution (as you read in the Cocoon2
- outline) is to have a regular expression based site map where site
+ outline) is to have a site map where site
managers decide what processing chain to apply to each possible request.
This somehow follows the mod_rewrite model in the Apache Web Server, but
rather than URL rewriting, the site map allows site designers to control the
@@ -99,24 +214,45 @@
</a>
</faq>
-<faq title="What is WAP and how do I browse WML?">
+<faq title="What is WAP and how do I browse WML?">
<q>What is WAP and how do I browse WML?</q>
<a>
<p>WAP stands for Wireless Application Protocol and WML stands for Wireless
Markup Language. For more information about these two, please refer to the
- <jump href="http://www.wapforum.org">WAP Forum</jump>. For a client able
+ <jump href="http://www.wapforum.org">WAP Forum</jump>. For a client able
to browse WML 1.1, Cocoon has been tested with the
- <jump href="http://www.nokia.com">Nokia WAP Toolkit</jump> which
+ <jump href="http://www.nokia.com">Nokia WAP Toolkit</jump> which
emulates a Nokia WAP cell phone on your desktop.</p>
</a>
</faq>
+
+<faq title="What is VoiceML and how do I browse VML?">
+<q>What is VoiceML and how do I browse VML?</q>
+<a>
+ <p>VoiceML and VML are the same and stand for "Voice Markup Language".
+ For more information, please refer to the
+ <jump href="http://www.voiceml.org">VoiceML Official web site</jump>.
+ The Cocoon VML samples have been tested with the
+ <jump href="http://www.voiceml.org">Motorola VoxML SDK 1.1</jump>(for windows)
+ which is freely available.</p>
+</a>
+</faq>
+
+<faq title="Why is my Internet Explorer not showing PDF or VRML samples?">
+<q>Why is my Internet Explorer not showing PDF or VRML samples?</q>
+<a>
+ <p>This is a long-time problem with internet explorer which, illegally,
+ reacts on URI extention rathen than returned MIME type. The only think you can
+ do for now is to map .pdf or .wrl to Cocoon for handling, but we know that
+ sucks. Don't worry, in the future, the sitemap proposal will allow you
+ to work around this magically. For now, just don't use IE :)</p>
+</a>
+</faq>
-<faq title="When I compile Cocoon on my system, I get all a bunch of errors. What's wrong?">
+<faq title="When I compile Cocoon on my system, I get all a bunch of errors. What's wrong?">
<q>When I compile Cocoon on my system, I get all a bunch of errors. What's wrong?</q>
<a>
- <p>You probably didn't add all the needed packages to your compiler's
- classpath or used the wrong version of the servlet classes (Cocoon is
- compiled with the Servlet 2.1 classes).
+ <p>You probably didn't add all the needed packages to your compiler's classpath.
Note that Cocoon supports much more packages than you normally use and you should have
them all to compile the full source code (this is why the cocoon.jar is distributed). To
avoid this, simply remove (or rename) the classes that wrap around the packages you don't
@@ -128,17 +264,19 @@
only way to compile it is to manually indicate all the files to compile or to use the
makefiles after removing the unwanted wrapper classes for the packages you don't have or
you don't want.</p>
+ <p>Note that Cocoon is built using Ant: please, refer to the build.xml file
+ for more information on how to set up your system to compile Cocoon</p>
</a>
</faq>
-<faq title="Why the name "Cocoon"?">
+<faq title="Why the name "Cocoon"?">
<q>Why the name "Cocoon"?</q>
<a>
<p> (Cocoon's creator Stefano Mazzocchi answers): It's a pretty stupid reason and a funny
story: I spent my 1998 Xmas vacation with my girlfriend up on the Alps at her cottage. One
night I couldn't sleep, I went to watch some TV and finishing reading the XSL
documentation I brought with me. Being a science fiction <ref>afficionado</ref>, I found out
- that Ron Howard's movie Cocoon was on and I started watching it. The idea of the XSL
+ that Ron Howard's movie <ref>Cocoon</ref> was on and I started watching it. The idea of the XSL
rendering servlet stoke me like the alien "cocoons" in the pool stroke those old men in the
movie and, while watching, I started paper-coding it right away. After a while the movie
was over and the publishing framework designed. The name "Cocoon" seemed right
1.4 +13 -13 xml-site/sources/cocoon/guide-sbk.xml
Index: guide-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/guide-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- guide-sbk.xml 1999/12/16 01:36:17 1.3
+++ guide-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,19 +1,19 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="User Guide">
+<s1 title="User Guide">
-<s2 title="Introduction">
+<s2 title="Introduction">
<p>This document assumes the knowledge of the W3C recommendation
- or working drafts used in Cocoon (mainly <jump href="http://www.w3.org/TR/REC-xml">XML</jump>,
- <jump href="http://www.w3.org/TR/WD-xsl">XSL</jump> in both its <jump href="http://www.w3.org/TR/WD-xslt">transformation</jump>
- and <jump href="http://www.w3.org/TR/WD-xsl">formatting</jump> capabilities). This
+ or working drafts used in Cocoon (mainly <jump href="http://www.w3.org/TR/REC-xml">XML</jump>,
+ <jump href="http://www.w3.org/TR/WD-xsl">XSL</jump> in both its <jump href="http://www.w3.org/TR/WD-xslt">transformation</jump>
+ and <jump href="http://www.w3.org/TR/WD-xsl">formatting</jump> capabilities). This
document is not intended to be an XML or XSL tutorial but just shows how these
technologies may be used inside the Cocoon framework to create web content.</p>
</s2>
-<s2 title="General overview">
+<s2 title="General overview">
<p>Cocoon is a publishing system that allows you to separate web development in three different
layers: content, style and logic.</p>
@@ -38,7 +38,7 @@
</source>
</s2>
-<s2 title="Hello World">
+<s2 title="Hello World">
<p>Every good user guide starts with an <code>Hello World</code> example and since we hope to
write good documentation (even if its hard like hell!), we start from there
too. Here is a well-formed XML file that uses a custom and simple DTD</p>
@@ -65,7 +65,7 @@
<p>On the other hand, we need to indicate how the presentation questions will
be answered. To do this, we must indicate a <ref>stylesheet</ref> that is able to
indicate how to interpret the elements found in this document. Thus, we
- follow a <jump href="http://www.w3.org/TR/WD-xml-stylesheet">W3C recommendation</jump>
+ follow a <jump href="http://www.w3.org/TR/WD-xml-stylesheet">W3C recommendation</jump>
and add the XML processing instruction to map a stylesheet to a document:</p>
<source><xml-stylesheet href"hello.xsl" type="text/xsl"></source>
@@ -153,7 +153,7 @@
</s2>
-<s2 title="Browser Dependent Styling">
+<s2 title="Browser Dependent Styling">
<p>When a document is processed by an XSLT processor, its output is exactly the same for every browser that requested
the page. Sometimes it's very helpful to be able to discriminate the client
capabilities and transform content layer into different views/formats. This is
@@ -224,11 +224,11 @@
more browsers may contain the same string.</p>
</s2>
- <s2 title="Cocoon Internals">
+ <s2 title="Cocoon Internals">
<p>The Cocoon publishing system has an engine based on the <ref>reactor</ref> design
pattern which is described in the picture below:</p>
- <p><img alt="Cocoon Schema" src="images/schema.jpg"/></p>
+ <p><img alt="Cocoon Schema" src="images/schema.jpg"/></p>
<p>Let's describe the components that appear on the schema:</p>
@@ -287,7 +287,7 @@
</ul>
</s2>
-<s2 title="Cocoon Processing Instructions">
+<s2 title="Cocoon Processing Instructions">
<p>The Cocoon reactor uses XML processing instructions to forward the document
to the right processor or formatter. These processing instructions are:</p>
@@ -354,7 +354,7 @@
</s2>
-<s2 title="Cocoon Cache System">
+<s2 title="Cocoon Cache System">
<p>In a complex server environment like Cocoon, performance and
memory usage are critical issues. Moreover, the processing requirement for
both XML parsing, XSLT transformations, document processing and formatting are
1.4 +23 -29 xml-site/sources/cocoon/index-sbk.xml
Index: index-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/index-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index-sbk.xml 1999/12/16 01:36:17 1.3
+++ index-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,11 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Cocoon">
+<s1 title="Cocoon">
- <s2 title="What is it?">
+ <s2 title="What is it?">
- <p><img alt="Cocoon" src="images/cocoon.jpg"/></p>
+ <p><img alt="Cocoon" src="images/cocoon.jpg"/></p>
<p>
Cocoon is a 100% pure Java publishing framework that relies on new W3C
@@ -27,7 +27,7 @@
</p>
</s2>
- <s2 title="What does it do?">
+ <s2 title="What does it do?">
<p>
Web content generation is mostly based on HTML, but HTML doesn't separate
the information from its presentation, mixing formatting tags, descriptive tags and
@@ -37,7 +37,7 @@
</p>
</s2>
- <s2 title="What does it change for me?">
+ <s2 title="What does it change for me?">
<p>
Even if the most common use of Cocoon is the automatic creation of HTML
through the processing of statically or dynamically generated XML files, Cocoon is also
@@ -78,7 +78,7 @@
</ul>
</s2>
- <s2 title="Are there any known problems?">
+ <s2 title="Are there any known problems?">
<p>
The biggest known problem in this framework is the lack of XML/XSL
knowledge, being relatively new formats. We do believe, though, that this publishing
@@ -106,15 +106,6 @@
of special cache systems.
</p>
<p>
- In this direction it must be understood that Cocoon 1.x should
- be considered a proof of concept rather than a software usable for real web
- sites. In fact, the Cocoon projects aims to gather as much information as
- possible during it's first generation while its second generation, starting
- from Cocoon 2.0, will aim to be a usable and real-life publishing framework.
- See the Cocoon 2 outline to understand the
- design plans already established.
- </p>
- <p>
Another problem is the intrinsic impossibility of page-compiling all the three
processing layers, due to the post-processing requirements of XSL styling. This
problem will be solved (hopefully!) with the availability of XSL-enabled
@@ -123,17 +114,17 @@
</p>
</s2>
- <s2 title="Where do I get it?">
+ <s2 title="Where do I get it?">
<p>
- Go to the <jump href="http://xml.apache.org/dist/">download area</jump>
+ Go to the <jump href="http://xml.apache.org/dist/">download area</jump>
and be sure you read the release note in that page.
</p>
</s2>
- <s2 title="How do I Contribute?">
+ <s2 title="How do I Contribute?">
<p>
The Cocoon Project is an open volunteer project based on the spirit of the
- <jump href="http://www.apache.org">Apache Software Foundation</jump> (ASF).
+ <jump href="http://www.apache.org">Apache Software Foundation</jump> (ASF).
This means that there are lots of ways to contribute to the project, either
with direct participation (coding, documenting, answering questions,
proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by resource
@@ -142,36 +133,39 @@
</p>
<p>
For direct participation, we suggest you to subscribe to the
- <jump href="http://xml.apache.org/mail.html">Cocoon mail lists</jump>
+ <jump href="http://xml.apache.org/mail.html">Cocoon mail lists</jump>
(follow the link for information on how to subscribe and to access the mail
- list archives), to checkout the <jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon/">
+ list archives), to checkout the <jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon/">
latest and greatest code</jump> (which you found in the xml-cocoon module in
- the xml.apache.org CVS code repository), control the todo
+ the xml.apache.org CVS code repository, or from the
+ <jump href="http://xml.apache.org/from-cvs/xml-cocoon/">CVS snapshots</jump>),
+ control the todo
list and jump in. Document writers are usually the most wanted people so if
- you like to help but you're not familiar with technical details, don't worry
+ you like to help but you're not familiar with technical details, don't worry:
we have work for you.
</p>
<p>
For money funding in particular, the Cocoon Project and the ASF in general
- is closely collaborating with the <jump href="http://www.sourcexchange.com">Collab.net
+ is closely collaborating with the <jump href="http://www.sourcexchange.com">Collab.net
SourceXchange</jump> program that will provide a legal, solid and well
established resource for money collecting to fund direct software production
under the open source flag. Please, feel free to contact directly Cocoon's
- main architect and project creator <jump href="mailto:stefano@apache.org">Stefano
- Mazzocchi</jump> or the ASF President and Collab.net co-founder <jump href="mailto:brian@collab.net">Brian
+ main architect and project creator <jump href="mailto:stefano@apache.org">Stefano
+ Mazzocchi</jump> or the ASF President and Collab.net co-founder <jump href="mailto:brian@collab.net">Brian
Behlendorf</jump> for more information on how to contribute directly to the
advancement of this project.
</p>
<p>
Anyway, a great way of contributing back to the project is to
- allow others to know about it so that the word spreads and other may wish to
+ allow others to know about it so that the word spreads and others may wish to
contribute, so, please, help us by placing the cocoon logo somewhere in your
- site to indicate that you are using uses and supporting the Cocoon Project.
+ site to indicate that you are using and supporting the Cocoon Project.
</p>
+
<p>
Thank you very much.
</p>
- <p><img alt="Powered by Cocoon" src="images/cocoon-small.jpg"/></p>
+ <p><img alt="Powered by Cocoon" src="images/cocoon-small.jpg"/></p>
</s2>
</s1>
1.4 +293 -86 xml-site/sources/cocoon/installing-sbk.xml
Index: installing-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/installing-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- installing-sbk.xml 1999/12/16 01:36:17 1.3
+++ installing-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Installing Cocoon">
+<s1 title="Installing Cocoon">
- <s2 title="System Requirements">
+ <s2 title="System Requirements">
<p>
Cocoon requires the following systems to be already installed in your
system:
@@ -25,7 +25,7 @@
</ul>
</s2>
- <s2 title="Required Components">
+ <s2 title="Required Components">
<p>
Cocoon is a publishing framework and was designed to be highly modular to
allow users to choose their preferred implementation for the required
@@ -40,69 +40,74 @@
<p><strong>XML Parsers</strong><table>
<tr>
- <th rowspan="1" colspan="1">Name</th>
- <th rowspan="1" colspan="1">Version</th>
- <th rowspan="1" colspan="1">Location</th>
+ <th rowspan="1" colspan="1">Name</th>
+ <th rowspan="1" colspan="1">Version</th>
+ <th rowspan="1" colspan="1">Location</th>
</tr>
<tr>
- <td rowspan="1" colspan="1">Apache Xerces</td>
- <td rowspan="1" colspan="1">1.0 (java edition)</td>
- <td rowspan="1" colspan="1"><jump href="http://xml.apache.org/dist/">xml.apache.org</jump></td>
+ <td rowspan="1" colspan="1">Apache Xerces</td>
+ <td rowspan="1" colspan="1">1.0.1 (java edition)</td>
+ <td rowspan="1" colspan="1"><jump href="http://xml.apache.org/dist/">xml.apache.org</jump></td>
</tr>
<tr>
- <td rowspan="1" colspan="1">Sun ProjectX</td>
- <td rowspan="1" colspan="1">TR2</td>
- <td rowspan="1" colspan="1"><jump href="http://java.sun.com/xml/">java.sun.com</jump></td>
+ <td rowspan="1" colspan="1">Sun ProjectX</td>
+ <td rowspan="1" colspan="1">TR2</td>
+ <td rowspan="1" colspan="1"><jump href="http://developer.java.sun.com/developer/products/xml/">java.sun.com</jump></td>
</tr>
<tr>
- <td rowspan="1" colspan="3">Cocoon comes preconfigured for Xerces</td>
+ <td rowspan="1" colspan="3">Cocoon comes preconfigured for Xerces</td>
</tr>
</table></p>
<p><strong>XSLT Processor</strong><table>
<tr>
- <th rowspan="1" colspan="1">Name</th>
- <th rowspan="1" colspan="1">Minimum Version</th>
- <th rowspan="1" colspan="1">Location</th>
+ <th rowspan="1" colspan="1">Name</th>
+ <th rowspan="1" colspan="1">Minimum Version</th>
+ <th rowspan="1" colspan="1">Location</th>
</tr>
<tr>
- <td rowspan="1" colspan="1">Apache Xalan</td>
- <td rowspan="1" colspan="1">0.19.1</td>
- <td rowspan="1" colspan="1"><jump href="http://xml.apache.org/dist/">xml.apache.org</jump></td>
+ <td rowspan="1" colspan="1">Apache Xalan</td>
+ <td rowspan="1" colspan="1">0.19.0</td>
+ <td rowspan="1" colspan="1"><jump href="http://xml.apache.org/dist/">xml.apache.org</jump></td>
</tr>
<tr>
- <td rowspan="1" colspan="1">James Clark's XT</td>
- <td rowspan="1" colspan="1">19991102</td>
- <td rowspan="1" colspan="1"><jump href="http://www.jclark.com/">www.jclark.com</jump></td>
+ <td rowspan="1" colspan="1">James Clark's XT</td>
+ <td rowspan="1" colspan="1">19991102</td>
+ <td rowspan="1" colspan="1"><jump href="http://www.jclark.com/">www.jclark.com</jump></td>
</tr>
<tr>
- <td rowspan="1" colspan="3">Cocoon comes preconfigured for Xalan</td>
+ <td rowspan="1" colspan="3">Cocoon comes preconfigured for Xalan</td>
</tr>
</table></p>
- <p><strong>Other Required Components</strong><table>
+ <p><strong>Other Packages</strong><table>
<tr>
- <th rowspan="1" colspan="1">Name</th>
- <th rowspan="1" colspan="1">Minimum Version</th>
- <th rowspan="1" colspan="1">Location</th>
+ <th rowspan="1" colspan="1">Name</th>
+ <th rowspan="1" colspan="1">Minimum Version</th>
+ <th rowspan="1" colspan="1">Location</th>
</tr>
<tr>
- <td rowspan="1" colspan="1">Apache FOP</td>
- <td rowspan="1" colspan="1">0.12.0</td>
- <td rowspan="1" colspan="1"><jump href="http://xml.apache.org/dist/">xml.apache.org</jump></td>
+ <td rowspan="1" colspan="1">Apache FOP</td>
+ <td rowspan="1" colspan="1">0.12.0</td>
+ <td rowspan="1" colspan="1"><jump href="http://xml.apache.org/dist/">xml.apache.org</jump></td>
</tr>
<tr>
- <td rowspan="1" colspan="1">FESI EcmaScript Engine</td>
- <td rowspan="1" colspan="1">1.2.1</td>
- <td rowspan="1" colspan="1"><jump href="http://home.worldcom.ch/jmlugrin/fesi/download.html">home.worldcom.ch/jmlugrin/fesi</jump></td>
+ <td rowspan="1" colspan="1">FESI EcmaScript Engine</td>
+ <td rowspan="1" colspan="1">1.2.1</td>
+ <td rowspan="1" colspan="1"><jump href="http://home.worldcom.ch/jmlugrin/fesi/download.html">home.worldcom.ch/jmlugrin/fesi</jump></td>
</tr>
<tr>
- <td rowspan="1" colspan="1">GNU Regexp</td>
- <td rowspan="1" colspan="1">1.0.8</td>
- <td rowspan="1" colspan="1"><jump href="http://www.cacas.org/java/gnu/regexp/">www.cacas.org/java/gnu/regexp</jump></td>
+ <td rowspan="1" colspan="1">GNU Regexp</td>
+ <td rowspan="1" colspan="1">1.0.8</td>
+ <td rowspan="1" colspan="1"><jump href="http://www.cacas.org/java/gnu/regexp/">www.cacas.org/java/gnu/regexp</jump></td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">JNDI API</td>
+ <td rowspan="1" colspan="1">1.2.1</td>
+ <td rowspan="1" colspan="1"><jump href="http://java.sun.com/products/jndi/index.html">java.sun.com</jump></td>
+ </tr>
</table></p>
<note>
@@ -122,12 +127,13 @@
</p>
<ul>
- <li>Apache Xerces (required for the formatting classes)</li>
+ <li>Apache Xerces (required for the formatting classes <ref>org.apache.xml.serialize</ref>)</li>
<li>Your favorite XML parser</li>
<li>Your favorite XSLT processor</li>
<li>Apache FOP (optional, unless you want PDF rendering)</li>
<li>GNU Regexp (optional, unless you use <ref>ProducerFromMap</ref>)</li>
<li>FESI (optional, unless you use <ref>DCP</ref>)</li>
+ <li>JNDI (optional, unless you use the <ref>LDAP processor</ref>)</li>
</ul>
<p>
@@ -136,7 +142,7 @@
</p>
</s2>
- <s2 title="Installing Cocoon">
+ <s2 title="Installing Cocoon">
<p>
Being Cocoon a servlet, you should be able to install it on every compliant
servlet engine by associating the "org.apache.cocoon.Cocoon" servlet
@@ -145,8 +151,90 @@
servlet systems.
</p>
- <s3 title="Installing Cocoon on Apache JServ">
+ <s3 title="General considerations">
+ <p>
+ There are some general considerations that apply to all systems.
+ </p>
+
+ <p>
+ Since there is no portable way, in a Java platform, to tell how much memory an object
+ is using, the memory cache works in a rather cumbersome manner: you set up
+ a lower limit that the cache must always leave free for the JVM operation.
+ This means, that if the memory limit is 200Kb, Cocoon uses all your JVM
+ heap size to store pages in memory and makes sure that 200Kb are available
+ for other operations.
+ </p>
+
+ <p>
+ This does not impact the JVM operation, if enough memory is left for the
+ normal operation. You must be aware of the fact that leaving Cocoon with
+ too little memory for operation does impact peformance since the JVM
+ garbage collector has to do more work to keep up with execution and
+ memory cleanup. Sometimes, you may even end up having OutOfMemoryExceptions
+ if your limit is lower than the memory required for the operation.
+ </p>
+
+ <p>
+ A good way to control your memory is to setup your JVM with a fixed
+ heap limit and to give it enough memory to start. This is done by using
+ command line parameters for your java interpreter such as:
+ </p>
+
+ <ul>
+ <li>Startup heap size:
+ <ul>
+ <li>java 1.1 - <code>-ms[size]</code></li>
+ <li>java 1.2 - <code>-Xms[size]</code></li>
+ </ul>
+ </li>
+ <li>Maximum heap size:
+ <ul>
+ <li>java 1.1 - <code>-mx[size]</code></li>
+ <li>java 1.2 - <code>-Xmx[size]</code></li>
+ </ul>
+ </li>
+ </ul>
+
<p>
+ A well balanced system should have something like 8Mb start heap, 2Mb
+ Cocoon memory limit and 64Mb or greater max heap, but these depend heavily
+ on your system load/configuration to be generally meaningful.
+ </p>
+
+ <p>
+ To change the cocoon object store memory limit open you should change the
+ following property in the <code>cocoon.properties</code> file.
+ </p>
+
+<source>store.memory = 200000</source>
+
+ <p>
+ Another important part of Cocoon is the page compiler used inside the
+ XSP processor which store the generated/compiled pages on file system.
+ The default directory is <code>./repository</code> which is usually relative
+ to the web server or servlet engine working directory.
+ </p>
+
+ <p>
+ If you experience
+ troubles (such as not having reading/writing permissions) or you want to
+ locate this directory somewhere else, you have to change the
+ </p>
+
+<source>processor.xsp.repository = ./repository</source>
+
+ <p>
+ property in the cocoon configuration file.
+ </p>
+
+ <p><em>Warning:</em>
+ Since this directory may contain security sensible information, make sure
+ you deny access (even read-only) to untrusted users.
+ </p>
+ </s3>
+
+ <s3 title="Installing Cocoon on Apache JServ">
+ <p>
Apache JServ has one configuration file for the whole engine (normally called
<code>jserv.properties</code>) and one for each servlet zone. Please, refer
to the Apache JServ documentation for more information on this.
@@ -173,6 +261,7 @@
wrapper.classpath=/usr/local/java/lib/xalan.jar
wrapper.classpath=/usr/local/java/lib/fop.jar
wrapper.classpath=/usr/local/java/lib/regexp.jar
+wrapper.classpath=/usr/local/java/lib/jndi.jar
</source>
<note>
@@ -201,10 +290,10 @@
<p>
Note that you should not need to change anything from the template
- properties file found in the distribution, but you must edit it for
- more complex operation. Please refer directly to the file that contains
- breaf indications and comments on the different configurations, but you
- don't need to care about that at this point.
+ properties file found in the distribution (under <code>/conf/</code>),
+ but you must edit it for more complex operation. Please refer directly to
+ the file that contains breaf indications and comments on the different
+ configurations, but you don't need to care about that at this point.
</p>
<p>
@@ -221,11 +310,20 @@
and <ref>/servlet/</ref> is the mount point of your servlet zone (and the
above is the standard name for servlet mapping for Apache JServ).
</p>
-
+
<p>
+ At this point, you should check if your system matches the global
+ considerations about Cocoon properties. Usually, you might want to give
+ the installation a try as it is and then read again that section if
+ something goes wrong. Most installations don't need any changes to
+ be operational.
+ </p>
+
+ <p>
Everything should be configured fine. Restart both Apache and Apache JServ
and try accessing the samples contained in the distribution to see
- Cocoon in action.
+ Cocoon in action or the <code>/Cocoon.xml</code> page for Cocoon internal
+ status.
</p>
<p>
@@ -245,7 +343,7 @@
</p>
</s3>
- <s3 title="Installing Cocoon on Apache Tomcat">
+ <s3 title="Installing Cocoon on Apache Tomcat">
<p>
Tomcat has two basic methods of locating Java classes for the runtime environment.
The first is the overall classpath that Tomcat uses to run, and this is the
@@ -281,10 +379,9 @@
Next you need to tell your context where Cocoon can find it's properties
file, as well as to map Cocoon to XML document requests.
Make sure you have a <ref>web.xml</ref> file in your context's
- <ref>WEB-INF</ref> directory. This file specifies servlet mappings
- and initial arguments to servlets. If you don't have this file, you can copy
- an example from <ref><Tomcat-Root>/examples/WEB-INF</ref>
- directory. You should add the following entries in that file:
+ <ref>WEB-INF</ref> directory (look in <code>src/WEB-INF/</code> to find a
+ template <ref>web.xml</ref>). This file specifies servlet mappings
+ and initial arguments to servlets and looks like this:
</p>
<source>
@@ -315,14 +412,32 @@
don't need to care about that at this point.
</p>
- <p>
- Everything should be configured fine. Restart Tomcat
- and try accessing the samples contained in the distribution to see
- Cocoon in action.
- </p>
+ <p>
+ At this point, you should check if your system matches the global
+ considerations about Cocoon properties. Usually, you might want to give
+ the installation a try as it is and then read again that section if
+ something goes wrong. Most installations don't need any changes to
+ be operational.
+ </p>
+
+ <p>
+ Everything should be configured fine. Restart both Apache and Tomcat
+ and try accessing the samples contained in the distribution to see
+ Cocoon in action or the <code>/Cocoon.xml</code> page for Cocoon internal
+ status.
+ </p>
+
+ <note><em>
+ Tomcat 3.0 has a bug that prevents Cocoon operation. In order to make
+ Cocoon work under Tomcat you need to download a newer version or, if
+ none is yet avaiable, build it from the latest source code found in the
+ <code>jakarta-tomcat</code> CVS module under <ref>jakarta.apache.org</ref>.
+ We apologize for this, but it's not something we can control or work
+ around.
+ </em></note>
</s3>
- <s3 title="Installing Cocoon on BEA WebLogic">
+ <s3 title="Installing Cocoon on BEA WebLogic">
<p>
After you have obtained all the jar packages you need (see the above
section), you should add all of them (included the <code>cocoon.jar</code>
@@ -342,53 +457,145 @@
making sure that you replaced <ref>[path-to-cocoon]</ref> with the actual
path in your system.
</p>
+
+ <p>
+ At this point, you should check if your system matches the global
+ considerations about Cocoon properties. Usually, you might want to give
+ the installation a try as it is and then read again that section if
+ something goes wrong. Most installations don't need any changes to
+ be operational.
+ </p>
+
<p>
- At this point your system is configured. Access the "/Cocoon.xml" page
- with your browser to see the Cocoon status screen that will tell you
- that Cocoon is up and running.
+ Everything should be configured fine. Restart Weblogic
+ and try accessing the samples contained in the distribution to see
+ Cocoon in action or the <code>/Cocoon.xml</code> page for Cocoon internal
+ status.
</p>
+
</s3>
- <s3 title="Installing Cocoon on Allaire JRun">
+ <s3 title="Installing Cocoon on other platforms">
<p>Yet to be written! <ref>Volunteers welcome!</ref></p>
</s3>
- <s3 title="Installing Cocoon on NewAtlanta ServletExec">
- <p>Yet to be written! <ref>Volunteers welcome!</ref></p>
- </s3>
-
</s2>
- <s2 title="Working Systems">
+ <s2 title="Working Systems">
<p>
Cocoon has been reported to be working on these systems:
</p>
- <ul>
- <li>RedHat Linux 6.0 + Apache 1.3.9 + Apache JServ 1.0 + IBM JDK 1.1.8</li>
- <li>RedHat Linux 6.0 + Apache 1.3.9 + Apache JServ 1.1b3 + IBM JDK 1.1.8</li>
- <li>RedHat Linux 6.0 + Apache 1.3.9 + Apache JServ 1.0 + Blackdown JDK 1.2pre2</li>
- <li>RedHat Linux 6.1 + Apache 1.3.9 + JRun 2.3.3 + IBM JRE 1.1.8</li>
- <li>Windows 98 + Apache 1.3.9 + Apache JServ 1.0 + IBM JDK 1.1.7</li>
- <li>Windows 98 + Apache 1.3.9 + Apache JServ 1.1b3 + IBM JDK 1.1.7</li>
- <li>Windows 98 + Apache 1.3.9 + Apache JServ 1.0 + Sun JDK 1.2.2</li>
- <li>Windows 98 + Apache 1.3.9 + Apache JServ 1.1b3 + Sun JDK 1.2.2</li>
- <li>Windows 98 + MS Personal Web Server + ServletExec 2.2 + Sun JDK 1.2.1</li>
- <li>Windows NT 4.0 + IIS 4.0 + ServletExec 2.2 + Sun JDK 1.2.1</li>
- <li>Windows NT 4.0 + IIS 4.0 + JRun 2.3.3 + Sun JDK 1.2.1</li>
- <li>Windows NT 4.0 + Apache 1.3.9 + JRun 2.3.3 + Sun JDK 1.2.2</li>
- <li>MacOS 8.6 + WebSTAR 4.0 + JRun 2.3 + MrJ 2.1.4</li>
- <li>MacOS 8.6 + WebSTAR 4.0 + ServletExec 2.1 + Mrj 2.1.4</li>
- <li>SunOS Netria 5.6 + Apache 1.3.9 + Apache JServ 1.1b3 + Sun JDK 1.1.7</li>
- <li>SCO OpenServer 5 + WebLogic 4.5.1 + SCO JDK 1.1.7A</li>
- </ul>
+ <p><strong/><table>
+ <tr>
+ <th rowspan="1" colspan="1">Operating System</th>
+ <th rowspan="1" colspan="1">Web Server</th>
+ <th rowspan="1" colspan="1">Servlet Engine</th>
+ <th rowspan="1" colspan="1">JVM</th>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">RedHat Linux 6.0</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.0</td>
+ <td rowspan="1" colspan="1">IBM JDK 1.1.8</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">RedHat Linux 6.0</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.1b3</td>
+ <td rowspan="1" colspan="1">IBM JDK 1.1.8</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">RedHat Linux 6.0</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.0</td>
+ <td rowspan="1" colspan="1">Blackdown JDK 1.2pre2</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">RedHat Linux 6.1</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">JRun 2.3.3</td>
+ <td rowspan="1" colspan="1">IBM JRE 1.1.8</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows 98</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.0</td>
+ <td rowspan="1" colspan="1">Sun JDK 1.2.2</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows 98</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.0</td>
+ <td rowspan="1" colspan="1">IBM JDK 1.1.7</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows 98</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.1b3</td>
+ <td rowspan="1" colspan="1">Sun JDK 1.2.2</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows 98</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.1b3</td>
+ <td rowspan="1" colspan="1">IBM JDK 1.1.7</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows 98</td>
+ <td rowspan="1" colspan="1">MS Personal Web Server</td>
+ <td rowspan="1" colspan="1">ServletExec 2.2</td>
+ <td rowspan="1" colspan="1">Sun JDK 1.2.1</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows NT 4.0</td>
+ <td rowspan="1" colspan="1">IIS 4.0</td>
+ <td rowspan="1" colspan="1">ServletExec 2.2</td>
+ <td rowspan="1" colspan="1">Sun JDK 1.2.1</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows NT 4.0</td>
+ <td rowspan="1" colspan="1">IIS 4.0</td>
+ <td rowspan="1" colspan="1">JRun 2.3.3</td>
+ <td rowspan="1" colspan="1">Sun JDK 1.2.1</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">Windows NT 4.0</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">JRun 2.3.3</td>
+ <td rowspan="1" colspan="1">Sun JDK 1.2.2</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">MacOS 8.6</td>
+ <td rowspan="1" colspan="1">WebSTAR 4.0</td>
+ <td rowspan="1" colspan="1">JRun 2.3</td>
+ <td rowspan="1" colspan="1">MrJ 2.1.4</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">MacOS 8.6</td>
+ <td rowspan="1" colspan="1">WebSTAR 4.0</td>
+ <td rowspan="1" colspan="1">ServletExec 2.1</td>
+ <td rowspan="1" colspan="1">Mrj 2.1.4</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">SunOS Netria 5.6</td>
+ <td rowspan="1" colspan="1">Apache 1.3.9</td>
+ <td rowspan="1" colspan="1">Apache JServ 1.1b3</td>
+ <td rowspan="1" colspan="1">Sun JDK 1.1.7</td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">SCO OpenServer 5</td>
+ <td rowspan="1" colspan="2">WebLogic 4.5.1</td>
+ <td rowspan="1" colspan="1">SCO JDK 1.1.7A</td>
+ </tr>
+ </table></p>
- <p>
- <ref>Note:</ref> due to a bug in <jump href="http://www.blackdown.org">Blackdown
+ <note>
+ Eue to a bug in <jump href="http://www.blackdown.org">Blackdown
JDK 1.2pre2</jump> for Linux, we suggest you to use green threads instead of the
native ones which are much less stable, expecially highly concurrent operations
like servlet engines and servlet execution.
- </p>
+ </note>
<p>
Please, submit your feedback if you were able to install Cocoon on a
different combination not listed above. Thanks.
1.4 +5 -5 xml-site/sources/cocoon/javadoc-sbk.xml
Index: javadoc-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/javadoc-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- javadoc-sbk.xml 1999/12/16 01:36:17 1.3
+++ javadoc-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,15 +1,15 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Javadoc Documentation in XML">
+<s1 title="Javadoc Documentation in XML">
- <s2 title="Introduction">
+ <s2 title="Introduction">
<p>We are currently working on enhancing the documentation provided for the
Cocoon XML publishing framework by converting javadoc commented source code into
XML for use within Cocoon.</p>
</s2>
- <s2 title="The plan">
+ <s2 title="The plan">
<p>In order to do this we are currently planning to implement the following
phases:</p>
@@ -55,7 +55,7 @@
</ol>
</s2>
- <s2 title="Progress to date">
+ <s2 title="Progress to date">
<p>
The first phase has been complete and a complete javadoc DTD was
created. We feel confortable with the solidity of that DTD and we plan
@@ -68,7 +68,7 @@
</p>
</s2>
- <s2 title="To do">
+ <s2 title="To do">
<p>
Being the first phase complete (the DTD is still in working-draft phase,
but it's complete and usable), we need to write the doclet, but the
1.4 +2 -2 xml-site/sources/cocoon/license-sbk.xml
Index: license-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/license-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- license-sbk.xml 1999/12/16 01:36:17 1.3
+++ license-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Cocoon Public License">
+<s1 title="Cocoon Public License">
-<s2 title="Cocoon Public License">
+<s2 title="Cocoon Public License">
<source>
============================================================================
The Apache Software License, Version 1.1
1.4 +10 -10 xml-site/sources/cocoon/sqlprocessor-sbk.xml
Index: sqlprocessor-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/sqlprocessor-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- sqlprocessor-sbk.xml 1999/12/16 01:36:17 1.3
+++ sqlprocessor-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,16 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="SQLProcessor">
+<s1 title="SQL Processor">
- <s2 title="Description">
+ <s2 title="Description">
<p>SQLProcessor is a processor for Cocoon that performs SQL queries, translates the resultset into an XML fragment, and inserts the fragment in the original document. I wrote it because I've got quite a bit of "legacy" data in SQL databases that I wanted to be able to easily access from Cocoon. I believe that servers and data structures capable of storing and retrieving large amounts of XML data natively will arise, obviating the need for this type of middleware. I also believe that it's going to take a while for them to achieve the same performance and stability we've come to expect from SQL databases, hence the current need for SQLProcessor or something like it.</p>
</s2>
- <s2 title="Installation">
+ <s2 title="Installation">
<p>Check your cocoon.properties for this line and add it if it's not already there:</p>
<source>processor.type.sql = org.apache.cocoon.processor.sql.SQLProcessor</source>
</s2>
- <s2 title="Configuration">
+ <s2 title="Configuration">
<p>Add this PI to the XML files to which you wish to add SQL queries:</p>
<source><?cocoon:process type="sql"?></source>
<p>You probably want this before any "xslt" processing directives. Then add SQL connection information to your XML files. The tagset for connection defitions looks like this:</p>
@@ -44,7 +44,7 @@
<p>You can also flag a querydefs node as the default for all query tags by setting the default attribute to yes. Note that query tags can always override the defaults.</p>
</s2>
- <s2 title="Usage">
+ <s2 title="Usage">
<p>Add SQL queries to your XML files. The tagset looks like this:</p>
<source><query connection="foo_connection">
select name,number,message from foo_table order by name
@@ -80,7 +80,7 @@
</ul>
</s2>
- <s2 title="Creating Complex Queries">
+ <s2 title="Creating Complex Queries">
<p>URL request parameter substitution using {@var} is fine for many situations, but is inadequate for handling queries whose conditions are dependent on the state of many variables. To accomodate these queries, you can specify the name of a subclass of SQLQueryCreator that will create the query string. The method that should be overridden is:</p>
<source>public String getQuery(Connection conn, String query,
Element query_element, Properties query_props, Hashtable parameters)
@@ -91,7 +91,7 @@
<p>This is probably an overly complex way to handle most complex queries. It is hopefully the case that a more sophisticated variable substitution scheme or alternate attribute set will arise that accomodates more common complex queries without the need to write Java code. There is also some rationale for making SQLQueryCreator an interface. I welcome suggestions along these lines.</p>
</s2>
- <s2 title="Error Handling">
+ <s2 title="Error Handling">
<p>In a perfect world, nothing would ever go wrong in your queries but this is not a perfect world. In our world, you can check for SQLExceptions in your stylesheets and present them to your users in a nice way. The tags used to render the error are configurable using attributes from the query tag. The attributes in question are:</p>
<ul>
<li><em>error-element</em> - The name of the error-element to create, default is sqlerror.</li>
@@ -105,11 +105,11 @@
<source><sqlerror message="The database server is on fire."/></source>
</s2>
- <s2 title="Notes and Disclaimers">
- <p>I sure hope this is useful to you. It's proving to be very useful to me. The DTD used here is a superset of that used by Oracle's XSQL servlet (which provides no methods for specifying alternate variable delimiters, creating complex queries, query default attributes, or error handling). Technical notes for the XSQL servlet are available - note you apparantly must now fill out an annoying survey to get access to this page. We're sharing the DTD with the tacit approval of Steve Meunch, who kindly pointed me in that direction when he saw a) how similar our methodologies were and b) how horrible my original DTD was. Thanks also go out to Stefano Mazzochi, who started this whole cocoon business in the first place, and Ricardo Rocha, whose DCP processor provided the framework for SQLProcessor's parent, XMLResultSet. Stefano Malimpensa has suggested many useful features that are beginning to make their way into the code.</p>
+ <s2 title="Notes and Disclaimers">
+ <p>I sure hope this is useful to you. It's proving to be very useful to me. The DTD used here is a superset of that used by Oracle's XSQL servlet (which provides no methods for specifying alternate variable delimiters, creating complex queries, query default attributes, or error handling). Technical notes for the XSQL servlet are available - note you apparantly must now fill out an annoying survey to get access to this page. We're sharing the DTD with the tacit approval of Steve Meunch, who kindly pointed me in that direction when he saw a) how similar our methodologies were and b) how horrible my original DTD was. Thanks also go out to Stefano Mazzocchi, who started this whole cocoon business in the first place, and Ricardo Rocha, whose DCP processor provided the framework for SQLProcessor's parent, XMLResultSet. Stefano Malimpensa has suggested many useful features that are beginning to make their way into the code.</p>
</s2>
- <s2 title="Planned Features">
+ <s2 title="Planned Features">
<ul>
<li>support for a <querydefs> tag for setting default query attributes</li>
<li>time-based caching of query results</li>
1.4 +279 -233 xml-site/sources/cocoon/technologies-sbk.xml
Index: technologies-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/technologies-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- technologies-sbk.xml 1999/12/16 01:36:17 1.3
+++ technologies-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,112 +1,140 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="Technologies Used">
-
-
+<s1 title="Technologies Used">
+
+
+
+<s2 title="Introduction">
+
+ <p>Since many people do not seem to understand the big picture of
+ the technologies used by Cocoon, I will try to explain my vision of
+ them. I will also provide some information that I hope will enable
+ you to jump right in, help with its development, or show your boss
+ how much money can be saved using Cocoon.</p>
+
+</s2>
-<s2 title="Introduction">
+<s2 title="What is this XML?">
-<p>Many people do not seem to understand the global picture about the
-technologies used by Cocoon, I will try to explain my vision of these
-technologies as well as some information that might be useful to you to jump in,
-help with its development or show your boss how much money he can save.</p>
-
- </s2>
-
-<s2 title="What is this XML?">
-
- <p>XML (<jump href="http://www.w3.org/markup/">eXtended Markup Language</jump>)
- is an SGML subset. SGML is the father of all
- markup languages and its a 15-years old ISO standard for creating languages.
- XML is a lighter version of SGML.</p>
-
- <p>First thing to understand: XML is NOT a language (like HTML), but a syntax.
- Exactly like ASCII that defines a standard way to map characters to bytes and
- not a bunch of character strings.</p>
-
-<p>XML is usually referred to as <ref>portable data</ref> in the sense that its
-parsing is <ref>application independent</ref> and one XML parser can read every
-possible XML document, one describing your bank account, another describing your
-favorite Italian meal, etc. This is, as you all know, impossible with other file
-formats which are text based or binary. Some sort of equivalent in the old days
-are CSV (comma separated values) files which use a very simple syntax (use comma
-to separate values and the first raw to outline the content of the columns) and
-are portable to every implementation. XML, unlike CSV, is much more flexible and
-structured even if it's much simpler than SGML.</p>
-
-<p>A particular XML language is defined by its Document Type Definition (DTD)
-which is described inside the XML specification. An XML document may be
-validated against a DTD (if present) and if the validation is successful the
-document is said <ref>valid XML based on the particular DTD</ref>, if a DTD is
-not present and the parser does not encounter syntax errors parsing the file,
-the XML document is said <ref>well-formed</ref>. If errors are found, the
-document is not XML compliant.</p>
-
-<p>So, any valid XML document is <ref>well-formed</ref> and an XML document <ref>valid
-</ref>for one particular DTD may not necessary be valid for another DTD.
-For example, HTML is not an XML language because the <code><br></code> tag
-is not XML compliant. XHTML (where <code><br></code> is replaced by <code><br/></code>)
-is XML compliant. While HTML pages are not always XML documents (some pages
-might be), XHTML pages are always well-formed and valid if matched against the
-XHTML DTD.</p>
+ <p>XML (<jump href="http://www.w3.org/XML/">eXtended Markup
+ Language</jump>) is a subset of SGML (<jump href="http://www.oasis-open.org/cover/general.html">Standard
+ Generalized Mark-up Language</jump>). SGML is the grandparent of
+ all markup languages and a 15-year-old <jump href="http://www.iso.ch/">ISO</jump> standard for creating
+ languages. You can think of XML as a lighter version of SGML.</p>
+
+ <p>The first thing you must understand is that XML is <ref>not</ref> a
+ language (like HTML), but a syntax, in the same way that ASCII
+ defines a standard way to map characters to bytes rather than to
+ character strings.</p>
+
+ <p>XML is usually referred to as <ref>portable data</ref> in the sense
+ that its parsing is <ref>application independent</ref>. The same XML
+ parser can read every possible XML document: one describing your
+ bank account, another describing your favorite Italian meal,
+ etc. This is, as you all know, impossible with other text-based or
+ binary file formats. A near-equivalent in the old days was CSV
+ (comma separated values) files, which used a very simple syntax (one
+ record per line, a comma separating fields, and the values in the
+ first row naming the columns). XML, unlike CSV, is much more
+ flexible and structured, even though it's much simpler than SGML.</p>
+
+ <p>A particular XML language is defined by its Document Type
+ Definition (DTD). DTDs are described in the XML specification.
+ They describe the syntax of a language implemented in XML. An XML
+ document may be validated against a DTD (if present). If the
+ validation is successful the document is said to be <ref>valid XML
+ based on the particular DTD</ref>. If a DTD is not present and the
+ parser does not encounter syntax errors parsing the file, the XML
+ document is said to be <ref>well-formed</ref>. If errors are found,
+ the document is not XML compliant.</p>
+
+ <p>So, any valid XML document is <ref>well-formed</ref> and an XML
+ document <ref>valid</ref> for one particular DTD may not necessarily
+ be valid for another DTD. For example, <jump href="http://www.w3.org/TR/REC-html40/">HTML</jump> is not an XML
+ language because some tags such as <code><br></code> are not
+ XML compliant. In <jump href="http://www.w3.org/TR/xhtml1/">XHTML</jump>, an XML compliant
+ reformulation of HTML, <code><br></code>, for example, is
+ replaced with <code><br/></code>. While HTML pages are not
+ always well-formed XML documents (some pages might be), XHTML pages
+ are always well-formed and valid XML documents if they match the
+ XHTML DTD.</p>
- <p>So far for the technical differences, but why HTML was not good enough?
- Let's make an example.</p>
+ <p>So much for the technical differences, but why was HTML not good
+ enough? Let's consider an example.</p>
</s2>
-<s2 title="XML shows its power">
- <p>Consider why the need for XML came about:</p>
+<s2 title="XML shows its power">
+
+ <p>Consider how the need for XML came about:</p>
+
<ul>
- <li>Everyone starts pubitemshing HTML documents on the web.</li>
+ <li>Everyone starts publishing HTML documents on the web.</li>
<li>Search engines spring up across the net to help find documents.</li>
<li>Search engines have a difficult time searching specific pieces of a
- document since HTML was designed to hierarchically represent how data
- should be presented, but not what the data being presented is.</li>
- <li>Web appitemcations spring up across the net to provide information and
+ document since HTML was designed to represent hierarchically how data
+ should be presented, but not what data is being presented.</li>
+ <li>Web applications spring up across the net to provide information and
<ref>services</ref>.</li>
</ul>
- <p>These services could be web pages that serve up important information about
- an organization or the structure of the organization. They could be weather
- information, or travel advisories. They could be contact information for
- people. Stock quotes. It could a book on how to grow the perfect Tomato.</p>
- <p>So now we have all this information. Tons of it. Great! Now go and search
- all these web pages for specific content, like Author or Subject. Find me all
- abstracts of any documents published that have a subject of <ref>Big Tomatoes</ref>,
- since I only want to view abstracts to find out which document is best for me.
- An HTML page is not designed for this. It was designed for <ref>how to present</ref>
- the data.</p>
- <p>When I look at a web page I might see that an author choose to make every
- paragraph heading bold with <code><font size+1></code>. Yet if I look at
- another page I might notice that every paragraph heading was marked up with <code><H1></code>.
- Yet another page may use tables and table headers to format the data. Find me
- every document that has the word <ref>potato</ref> in the paragraph heading
- of the first paragraph.</p>
- <p>Suppose I have a weather web-based application that servers up weather
- information for different parts of the country. Let's say you live in Boston,
- MA and only want the weather for Boston. Your boss asks you to write an
- application that goes out and grabs the two-three sentence weather summary
- from my application and display this on your intranet's homepage.</p>
- <p>You take a quick jaunt over to my weather application and notice that the
- summary is in what looks like the second paragraph of the page. So you take a
- quick peek at the HTML source that my weather application returned. You
- suddenly realize that it's all on one line, and is buried deep within tables.</p>
- <p>So you start writing your little application that parses my HTML code to
- retrieve just the information you were looking for. You pat yourself on the
- back when 4 hours later you finally get the information you were look for.
- Your code looks for the 2nd Table, the 6th TR and then the 2nd TD. Phew. Your
- application, that only wants weather data, is forced to parse display markup
- to get the data it needs.</p>
- <p>You run over to your boss and show him your application that you are so
- proud that you wrote. Low and behold it doesn't work. What happened? Good old
- path author decided to change his display and put the weather summary in Table
- 1, TR 1, TD 1. Your application broke because it was tied to the presentation
- of the data and not to the data itself. Not very effective. Since now your app
- will break every time the page author drinks too much coffee.</p>
- <p>Then you notice, something on the page that interests you. This site was
- automatically generated from XML and you see a link that says XML DTD for
- weather information. And another link that says XML stream for weather
- information available. Yikes, would you look at that:</p>
+
+ <p>These services could be web pages that serve up important
+ information about an organization or the structure of the
+ organization. It could be weather information or travel
+ advisories. It could be contact information for people. Stock
+ quotes. It could a book on how to grow the perfect Tomato.</p>
+
+ <p>So now we have all this information. Tons of it. Great! Now go
+ and search all those web pages for specific content, like Author or
+ Subject. Find me all abstracts of documents published on the subject
+ of <ref>Big Tomatoes</ref>, since I only want to view abstracts to
+ find the document best for me. An HTML page is not designed for
+ this. It was designed for <ref>how to present</ref> the data.</p>
+
+ <p>When I look at a web page I might see that an author chose to
+ make every heading bold with <code><font
+ size="+1"></code>. Yet if I look at another page I might notice
+ that every heading was marked up with <code><H1></code>. Yet
+ another page may use tables and table headers to format the
+ data. Find me every document that has the word <ref>potato</ref> in
+ the first heading.</p>
+
+ <p>Suppose I have a web application that serves up weather
+ information for different parts of the country. Let's say you live
+ in Boston, MA and only want the local weather. Your boss asks you to
+ write an application that goes out and grabs the two-to-three
+ sentence weather summary from my application and display it on your
+ intranet's homepage.</p>
+
+ <p>You take a quick jaunt over to my weather application and notice
+ that the summary is in what looks like the second paragraph of the
+ page. So you take a quick peek at the HTML source that my weather
+ application returns. You suddenly realize that it's all on one line
+ and is buried deep within tables.</p>
+
+ <p>So you start writing your little application to parse my HTML
+ code to retrieve only the information you were looking for. You pat
+ yourself on the back when—4 hours later—you finally get
+ the information you were looking for. Your code looks for the 2nd
+ <code>TABLE</code>, the 6th <code>TR</code>, and then the 2nd
+ <code>TD</code>. Phew. Your application, which really only wants to
+ retrieve weather data, is forced to parse display markup to get
+ it.</p>
+
+ <p>You run over to your boss and demonstrate the application you are
+ so proud of writing. Lo and behold it doesn't work. What happened?
+ The good old page author decided to change the layout and move the
+ weather summary to <code>TABLE</code> 1, <code>TR</code> 1,
+ <code>TD</code> 1. Your application breaks because it is tied to the
+ presentation of the data and not to the data itself. Not very
+ effective, since now your app will break every time the page author
+ drinks too much coffee.</p>
+
+ <p>Then you notice something on the page that interests you. The
+ site is automatically generated from XML and you see a link that
+ indicates there is an XML DTD for weather information. And another
+ link that indicates the availability of an XML stream for weather
+ information. Yikes, would you look at that:</p>
<source>
<weather-information>
@@ -121,7 +149,8 @@
</weather-information>
</source>
- <p>So you download Cocoon, simply write an XSL stylesheet that looks the the following:</p>
+ <p>So you simply download Cocoon and quickly write an XSL stylesheet
+ that looks like the following:</p>
<source>
<xsl:stylesheet>
@@ -136,172 +165,189 @@
</source>
<p>And your boss gives you your job back! ;-)</p>
- </s2>
+
+</s2>
+
+<s2 title="The HTML Model">
+
+ <p>As the above example explains, HTML is a language for describing
+ graphics, behavior, and hyperlinks on web pages. HTML is
+ <ref>not</ref> able to <ref>contextualize</ref> (i.e. <ref>give meaning
+ to some text</ref>). For example, if you look for the <ref>title</ref>
+ of a page, a nice HTML tag gives you that, but if you look for the
+ author or version or something more specific like the author's mail
+ address—even if this information is present in the
+ text—you don't have a way to <ref>isolate</ref> it
+ (contextualize it) from the surrounding information.</p>
-<s2 title="The HTML Model">
+ <p>In HTML like this</p>
-<p>As the above example explains very well, HTML is a language for describing
-graphics, behavior and hyperlinks on web pages. HTML is NOT able to <ref>contextualize</ref>
-(means <ref>give meaning to some text</ref>) in the sense that if you look for
-the <ref>title</ref> of your page, a nice HTML tag gives you that, but if you
-look at the author or version or something more specific like the author mail
-address, even if this information is present in the text you don't have a way to
-<ref>isolate</ref> this (contextualize it) from the surrounding information.</p>
-
-<p>In some HTML like this</p>
-
-<source>
- <html>
- <head>
+ <source>
+ <html>
+ <head>
+ <title>This is my article</title>
+ </head>
+ <body>
+ <h1 align="center">This is my article</h1>
+ <h3 align="center">
+ by <a href="mailto:stefano@apache.org">
+ Stefano Mazzocchi
+ </a>
+ </h3>
+ ...
+ </body>
+ </html>
+ </source>
+
+ <p>you don't have a guaranteed way to extract the mail address.
+ Whereas in the following XML document</p>
+
+ <source>
+ <?xml version="1.0"?>
+ <page>
<title>This is my article</title>
- </head>
- <body>
- <h1 align="center">This is my article</h1>
- <h3 align="center>
- by <a href="mailto:stefano@apache.org">
- Stefano Mazzocchi
- </a>
- </h3>
+ <author>
+ <name>Stefano Mazzocchi</name>
+ <mail>stefano@apache.org</mail>
+ </author>
...
- </body>
- </html>
-</source>
-
-<p>you don't have a guaranteed way to extract the mail address, while in the
-following XML document</p>
-
-<source>
- <?xml version="1.0"?>
- <page>
- <title>This is my article</title>
- <author>
- <name>Stefano Mazzocchi</name>
- <mail>stefano@apache.org</mail>
- </author>
- ...
- </page>
-</source>
+ </page>
+ </source>
-<p>it's trivial and algorithmically certain.</p>
+ <p>it's trivial and algorithmically certain.</p>
-<p>We don't picture XML take over HTML in web publishing since HTML is great for
-small needs. HTML was born as an SGML-based DTD for scientists homepages. HTML
-was NOT designed for publishing and treatment of large quantity of data and
-complex dynamic information systems, but only to parallelize and simplify the
-deployment and management of personal information.</p>
+ <p>We don't imagine XML overtaking HTML in web publishing since HTML
+ is great for small needs. HTML was born as an SGML-based DTD for
+ scientists' homepages, i.e. to parallelize and simplify the
+ deployment and management of personal information. HTML was
+ <ref>not</ref> designed for the publishing and processing of large
+ quantities of data and complex dynamic information systems.</p>
</s2>
-<s2 title="The XSL Language">
+<s2 title="The XSL Language">
-<p>As you see, XML alone is useless without some defined semantics: even if an
-application is able to parse a document in memory, it must be able to <ref>understand</ref>
-that the markup means. This is why XML-only browsers are meaningless and not
-more useful than text editors from an usability point of view.</p>
-
-<p>This is one of the reasons why the XSL language (<jump href="http://www.w3.org/style/xsl/">eXtensible Stylesheet
-Language</jump>) was proposed and designed. XSL is divided in two parts: transformation (XSLT) and
-formatting objects (sometimes referred to FO, XSL:FO or simply XSL). Both are
-XML DTDs that define a particular XML syntax. So every XSL and XSLT document is
-a well-formed XML document.</p>
+ <p>As you can see, XML alone is useless without some defined
+ semantics: even if an application is able to parse a document, it
+ must be able to <ref>understand</ref> what the markup means. This is
+ why XML-only browsers are meaningless and not more useful than text
+ editors from a usability point of view.</p>
+
+ <p>This is one of the reasons why XSL (the <jump href="http://www.w3.org/style/xsl/">eXtensible Stylesheet
+ Language</jump>) was proposed and designed. XSL is divided into two
+ parts: <jump href="http://www.w3.org/TR/xslt">transformation</jump>
+ (XSLT) and <jump href="http://www.w3.org/TR/WD-xsl/">formatting
+ objects</jump> (sometimes referred to as FO, XSL:FO, or simply
+ XSL). Both are XML DTDs that define a particular XML syntax, so
+ every XSL or XSLT document is a well-formed XML document.</p>
</s2>
+
+<s2 title="XSL Transformations (XSLT)">
-<s2 title="XSL Transformations (XSLT)">
+ <p>XSLT is a language for transforming one well-formed XML document
+ into something else (which may <ref>not</ref> necessarily be another
+ XML document, although it most often will be). This means that you
+ can use it to go from one DTD to another in a procedural way that is
+ defined inside your XSLT document. XSLT can be used in ways its
+ name might not imply: a transformation may be applied to a document
+ to generate a <ref>graphical description</ref> of its content. This is
+ called <ref>styling</ref>, but, as you can imagine, it is just one of
+ the possible uses of transformation technology.</p>
+
+ <p>Back in the earlier example, the HTML file may have been
+ generated from an XML file using <ref>another</ref> XML file as a
+ transformation sheet (which in this case is a stylesheet). The data
+ is all there: we just have to tell the transformer how to come up
+ with the HTML document once all the data is parsed.</p>
+
+ <p>Usually, transformation sheets work from one DTD to another and
+ in this way form a chain: transformA goes from DTD1 to DTD2 and
+ transformB from DTD2 to DTD3 or graphically</p>
-<p>XSLT is a language for transforming one well-formed XML document into
-something else. This means that you may use it to go from one DTD to another in an procedural way
-that is defined inside your XSLT document. Even if the name tells the opposite,
-this language can be used for document styling as well as for many other useful
-transformations: in fact, transformations may be applied to one particular XML
-DTD and come up with some <ref>graphical description</ref> of the original
-content. This is called <ref>styling</ref>, but, as you can see, this is just
-one of the possible uses of the technology.</p>
-
-<p>For example, the above HTML example may be created from the second XML file
-given a particular transformation sheet (which in this case becomes a
-stylesheet). As you can see, the data is all there: we just have to tell the
-transformer how to come up with the HTML document once all the data is parsed in
-memory.</p>
-
-<p>Usually, transformation sheets work from one DTD to another and for this
-reason may be used in chain: transformA goes from DTD1 to DTD2 and transformB
-from DTD2 to DTD3 or graphically</p>
-
-<source>DTD1 ---(transformA)--> DTD2 ---(transformB)---> DTD3</source>
-
-<p>We'll call DTD1 the <ref>original DTD</ref> (because its the origin), DTD2 some <ref>intermediate
-DTD</ref>, DTD3 the <ref>final DTD</ref>. It can be shown that a transformation can
-always be created to go directly from DTD1 to DTD3, but this might be more
-complicated and less human readable/manageable.</p>
+
+ <source>DTD1 ---(transformA)--> DTD2 ---(transformB)---> DTD3</source>
+
+ <p>We'll call DTD1 the <ref>original DTD</ref>, DTD2 some
+ <ref>intermediate DTD</ref>, DTD3 the <ref>final DTD</ref>. A
+ transformation can always be created to go directly from DTD1 to
+ DTD3, but this might be more complicated and less
+ human-readable/manageable.</p>
</s2>
-<s2 title="XSL Formatting Objects (XSL:FO)">
+<s2 title="XSL Formatting Objects (XSL:FO)">
-<p>XSLFO is a language (an XML DTD) for describing 2D graphics of text in both
-printed and digital media. I will not concentrate on the graphical abilities
-that formatting objects gives you, but rather on the fact that it is most of the
-time used as a <ref>final DTD</ref>, meaning that a transformation is used to
-generate a formatting object description of a document starting from a general
-XML file.</p>
+ <p>XSLFO is a language (an XML DTD) for describing 2D layout of text
+ in both printed and digital media. I will not concentrate on the
+ graphical abilities that formatting objects give you, but rather on
+ the fact that it is mostly used as a <ref>final DTD</ref>, meaning
+ that a transformation is used to generate a formatting object
+ description of a document starting from a general XML file.</p>
-<p>The example above would lead:</p>
+ <p>An XSLFO document for our ongoing example would be</p>
-<source>
- <?xml version="1.0"?>
+ <source>
+ <?xml version="1.0"?>
<fo:root xmlns:fo="http://www.w3.org/XSL/Format/1.0">
- ...
- <fo:flow font-size="14pt" line-height="14pt">
- <fo:block
- text-align="centered"
- font-size="24pt"
- line-height="28pt">This is my article</fo:block>
- <fo:block
- space-before.optimum="12pt"
- text-align="centered">by Stefano Mazzocchi</fo:block>
- </fo:flow>
+ ...
+ <fo:flow font-size="14pt" line-height="14pt">
+ <fo:block
+ text-align="centered"
+ font-size="24pt"
+ line-height="28pt">This is my article</fo:block>
+ <fo:block
+ space-before.optimum="12pt"
+ text-align="centered">by Stefano Mazzocchi</fo:block>
+ </fo:flow>
</fo:root>
-</source>
+ </source>
- <p>which tells the formatting object formatter (the rendering engine), how to
- <ref>draw</ref> and place the text on the screen or on paper. Formatting
- objects and transformations are created by the same working group and show
- very high synergies even if the XSLT specification also includes way to create
- HTML and text out of XML files as well.</p>
+ <p>which tells the formatting object formatter (the rendering
+ engine), how to <ref>draw</ref> and place the text on screen or on
+ paper.</p>
+
+ <p>XSL formatting objects and transformations are being specified by
+ the same working group and have a lot of synergy, even though the
+ XSLT specification also includes ways to create HTML and text from
+ XML files.</p>
</s2>
+<s2 title="The XSP Language">
+
+ <p>The Cocoon publishing model is heavily based on the XSLT
+ transformation capabilities. XSLT allows complete separation of
+ content and style (something that is much harder to obtain with
+ HTML, even using CSS2 or other styling technologies). But Cocoon
+ goes further and defines a way of separating content and style from
+ the programming logic that drives server side behavior.</p>
+
+ <p>The XSP language (eXtensible Server
+ Pages) defines an XML DTD for separating content and logic
+ for compiled server pages.
-<s2 title="The XSP Language">
+
- <p>The Cocoon publishing model is heavily based on the XSLT transformation
- capabilities that allow complete separation of content and style (something
- that is much harder to obtain with HTML even using CSS2 or other styling
- technologies) but it moved on to defined a way to separate page content and
- document tags from the programming logic that drive their server side
- behavior.</p>
-
- <p>The XSP language (eXtensible Server Pages)
- languages defines an XML DTD for separating content and logic for compiled server pages.
- XSP (eXtensible Server Pages) is, like XSLFO, supposed to be a <ref>final
- DTD</ref> in the sense that is the result of one or more transformation steps
- and must be rendered by some formatter into pure source code that can then be
+ XSP is, like XSLFO, supposed to be a <ref>final DTD</ref>, in that it
+ is the result of one or more transformation steps and must be
+ rendered by some formatter into pure source code which can then be
compiled into binary code.</p>
- <p>In every dynamic page, there is a mix of static content and logic that work
- together to create the final result, usually using run-time or
- time-dependent input. In dynamic content generation technology, content and
- logic are mixed in the same page. XSP is no exception since it defines a
- syntax to mix static content and programmatic logic in a way that is independent
- of the programming language used and on the binary results that the final
- source-rendering gives.</p>
-
- <p>But it must be understood that XSP is just a piece of the framework:
- exactly like formatting objects mix style and content, XSP mix logic and
- content. On the other hand, being both XML DTDs, XSLT can be used to move from
- pure content to these final DTDs, placing the style and logic on the
- transformation layers and guaranteeing complete separation and easier
+ <p>In dynamic content generation technology, content and logic are
+ combined: in every page there is a mix of static content and dynamic
+ logic that work together to create the final result, usually using
+ run-time or time-dependent input. XSP is no exception, since it
+ defines a syntax to mix static content and programmatic logic in a
+ way that is independent of both the programming language used and
+ the binary results that the final source-rendering generated.</p>
+
+ <p>But it must be understood that XSP is just a piece of the
+ framework: exactly like how formatting objects mix style and
+ content, XSP objects mix logic and content. On the other hand, since
+ both are XML DTDs, XSLT can be used to move from pure content to
+ these final DTDs, placing the style and logic on the transformation
+ layers and guaranteeing complete separation and easier
maintenance.</p>
</s2>
1.4 +34 -18 xml-site/sources/cocoon/todo-sbk.xml
Index: todo-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/todo-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- todo-sbk.xml 1999/12/16 01:36:17 1.3
+++ todo-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,18 +1,34 @@
-<s1 title="Todo List"><s2 title="showstopper"><li><em>docs</em> -
- Finish XML-ize the docs (DCP, SQL).
- </li></s2><s2 title="high"><li><em>code</em> -
- Implement "xsl:output" instead of "cocoon-format" PI and redesign
- formatting subsystem.
- </li><li><em>code</em> -
- Pass request/session parameters to the XSLT processors for dynamic
- stylesheet operation.
- </li><li><em>code</em> -
- Work on external entities inclusion (follows sitemap stuff).
- </li></s2><s2 title="medium"><li><em>design</em> -
- Write SiteMap document.
- </li><li><em>design</em> -
- Merge stylebook technology with Cocoon
- </li></s2><s2 title="low"><li><em>code</em> -
- make the error page formatted with the wanted mime type and not only HTML
- (probably impossible in Cocoon1 model)
- </li></s2></s1>
\ No newline at end of file
+<?xml version="1.0" encoding="UTF-8"?>
+<s1 title="Todo List">
+
+
+
+
+
+
+
+ <s2 title="high"><li><em>code</em> -
+ Implement the sitemap.
+ </li><li><em>code</em> -
+ Move everything under SAX and build SAX2DOM and DOM2SAX adaptors (hopefully
+ using some Xerces code for this).
+ </li><li><em>code</em> -
+ Pass request/session parameters to the XSLT processors for dynamic
+ stylesheet operation. (follows sitemap)
+ </li><li><em>code</em> -
+ Fix problems on Xalan liaison that breaks <xsl:import> (follows SAX usage).
+ </li><li><em>code</em> -
+ Create a caching virtual URL file system for external inclusions.
+ </li></s2>
+
+ <s2 title="medium"><li><em>code</em> -
+ Implement the error handler subsystem
+ </li><li><em>design</em> -
+ Merge stylebook technology with Cocoon
+ </li></s2>
+
+ <s2 title="low"><li><em>docs</em> -
+ Make the section title an element to allow entities to be included
+ </li></s2>
+
+</s1>
\ No newline at end of file
1.4 +44 -45 xml-site/sources/cocoon/WD-xsp-sbk.xml
Index: WD-xsp-sbk.xml
===================================================================
RCS file: /home/cvs/xml-site/sources/cocoon/WD-xsp-sbk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- WD-xsp-sbk.xml 1999/12/16 01:36:16 1.3
+++ WD-xsp-sbk.xml 2000/01/18 16:57:14 1.4
@@ -1,9 +1,19 @@
<?xml version="1.0" encoding="UTF-8"?>
-<s1 title="XSP Layer 1">
+<s1 title="eXtensible Server Pages">
+ <s2 title=""><table><tr><th>Authors</th></tr><tr><td><strong>Stefano Mazzocchi</strong> - stefano@apache.org</td></tr><tr><td><strong>Ricardo Rocha</strong> - ricardo@apache.org</td></tr><tr><th>Status</th></tr><tr><td><strong>Working Draft - 2000-01-09</strong></td></tr><tr><th>Notice</th></tr><tr><td>
+ This is an Apache Working Draft for review by all interested
+ parties. It is a draft document and may be updated, replaced, or obsoleted by other
+ documents at any time. It is inappropriate to use Working Drafts as reference material or
+ to cite them as other than "work in progress". This work is part of the Apache Cocoon Project
+ </td></tr><tr><th>Abstract</th></tr><tr><td>
+ This document specifies an XML namespace that addresses a complete
+ region of web publishing, that of logic-based, dynamic content generation. This language
+ is introduced to fill an existing gap between the W3C specifications and working draft and
+ the increasing demand for a flexible server side approach based on the new XML paradigm.
+ </td></tr></table></s2>
-
- <s2 title="Introduction">
+ <s2 title="Introduction">
<p>This document specifies both an XML document type definition and a development
methodology to generate dynamic XML by server side processing of client's requests. Such a
specification is useful to define an open and standard way to develop and maintain dynamic
@@ -12,7 +22,7 @@
on this project, even if the final goal of this effort is to submit a request to a standard
body (such as W3C) for final recommendation.</p>
- <s3 title="Origins">
+ <s3 title="Origins">
<p>The need for an open language to standardizing server side programmatic XML generation
was observed when XML-based web publishing frameworks emerged and no available technology
was detailed, stable, useful and open enough to be used. XSP, by mixing Turing-complete
@@ -29,7 +39,7 @@
completely transparent to the namespaces/document-types used.</p>
</s3>
-<s3 title="Layer Separation">
+<s3 title="Layer Separation">
<p>Being a rather complex technology, the XSP specification will be separated into layers.
These layers will have different goals and restrictions and will allow faster development
cycles and a better defined development model. Every layer will define its own document
@@ -38,7 +48,7 @@
programming languages range from higher-levels to lower-levels.</p>
</s3>
-<s3 title="General Goals">
+<s3 title="General Goals">
<p>Following is a summary of the design principles governing the general XSP specification:</p>
<ol>
<li>should integrate completely with existing W3C recommendations and working drafts</li>
@@ -54,7 +64,7 @@
</ol>
</s3>
-<s3 title="Layer 1 Goals">
+<s3 title="Layer 1 Goals">
<p>Following is a summary of the design principles governing the Layer 1 of the XSP
specification:</p>
<ol>
@@ -76,7 +86,7 @@
</ol>
</s3>
-<s3 title="Layer 2 Goals">
+<s3 title="Layer 2 Goals">
<p>Following is a summary of the design principles governing the Layer 2 of the XSP
specification:</p>
@@ -98,7 +108,7 @@
</ol>
</s3>
-<s3 title="Final Goals">
+<s3 title="Final Goals">
<p>The XSP specification would eventually evolve into a single specification with a single
document type definition. This will happen when the working draft phase will be terminated
and all involved parties will agree on the specification stability. The Layer 1 will be
@@ -106,7 +116,7 @@
probably need several evolution stages to reach their final shape.</p>
</s3>
-<s3 title="Relationship to Existing Standards">
+<s3 title="Relationship to Existing Standards">
<p>Three standards have been especially influential:</p>
<ul>
<li><em>JSP</em> - defines a way to embed programmatic logic into web documents.</li>
@@ -121,7 +131,7 @@
especially WebMacro and GSP.</p>
</s3>
-<s3 title="Terminology">
+<s3 title="Terminology">
<p>The following basic terms apply in this document:</p>
<ul>
<li><em>document</em> -
@@ -161,9 +171,9 @@
</s3>
</s2>
-<s2 title="XSP Syntax and DTD">
+<s2 title="XSP Syntax and DTD">
-<s3 title="Defined External Entities">
+<s3 title="Defined External Entities">
<p>The XSP specification defines some external entities that may be used to reduce the
verbosity of XSP document, allowing the inclusion the default DTD via entity mapping. The
@@ -171,14 +181,14 @@
<source>
<!DOCTYPE page PUBLIC
- "-//Apache//DTD XSP Layer 1//EN"
- "http://www.apache.org/1999/XSP/Layer1"
+ "-//Apache//DTD XSP//EN"
+ "http://www.apache.org/1999/XSP/Core"
>
</source>
</s3>
-<s3 title="The XSP Layer 1 Document Type Definition">
+<s3 title="The XSP Layer 1 Document Type Definition">
<p>The XSP DTD was designed with simplicity in mind. The number of elements and attributes
was reduced to a minimum to allow a fast and easy learning process. On the other hand, no
special helper elements were defined in Layer 1 to reduce the spec development time and to
@@ -199,10 +209,8 @@
<!ELEMENT xsp:page (xsp:structure?, xsp:logic?, xsp:content)>
<!ATTLIST xsp:page
language CDATA #REQUIRED
- result-ns NMTOKEN #IMPLIED
- default-space (preserve|strip) "preserve"
indent-result (yes|no) "no"
- xmlns:xsp CDATA #FIXED "http://www.apache.org/1999/XSP/Layer1"
+ xmlns:xsp CDATA #FIXED "http://www.apache.org/1999/XSP/Core"
xml:space (default|preserve) "preserve"
>
@@ -238,7 +246,7 @@
</s3>
</s2>
-<s2 title="Example of Usage">
+<s2 title="Example of Usage">
<p>Consider the following XML source document:</p>
<source>
@@ -263,10 +271,9 @@
<source>
<?xml version="1.0"?>
-<xsl:transformation
- xmlns:xsl="http://www.w3.org/1999/XSL/tranform"
- xmlns:xsp="http://www.apache.org/1999/XSP/Layer1"
- result-ns="http://www.apache.org/1999/XSP/Layer1"
+<xsl:transform
+ xmlns:xsl="http://www.w3.org/1999/XSL/Tranform"
+ xmlns:xsp="http://www.apache.org/1999/XSP/Core"
>
<xsl:template match="page">
@@ -302,7 +309,7 @@
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>
-</xsl:transformation>
+</xsl:transform>
</source>
<p>After applying the above logic sheet, the resulting document would be equivalent to the
@@ -483,7 +490,7 @@
performance) in every XSP engine.</p>
</s2>
-<s2 title="XSP and JSP">
+<s2 title="XSP and JSP">
<p>XSP and JSP might appear as overlapping at a first glance since they both:</p>
<ul>
@@ -497,7 +504,7 @@
<p>While these are very important points were the two specifications <ref>do</ref>
overlap, there are significant differences described hereafter.</p>
-<s3 title="Output Exposure">
+<s3 title="Output Exposure">
<p>In all different server pages technologies, some data regarding the status
of the resource are available to page logic. Since JSP follow the Servlet API
model, expecting JSP pages to be compiled into servlets, the same data
@@ -526,7 +533,7 @@
JSP always require.</p>
</s3>
-<s3 title="Page Readability">
+<s3 title="Page Readability">
<p>For these reasons, XSP, unlike JSP, uses the XML feature of <ref>syntax
orthogonalily</ref> that allows almost any programming language code to be
easily distinguishable between markup elements, while JSP needs to enclose
@@ -603,33 +610,25 @@
<s2 title="">
-<s2 title="Normative References">
+<s2 title="Normative References">
<ul>
- <li><em>[<jump href="http://www.w3.org/TR/REC-DOM-Level-1">DOM</jump>]</em> "Document Object Model (DOM) Level 1 Specification", Lauren Wood et al., 1 October 1998</li>
+ <li><em>[<jump href="http://www.w3.org/TR/REC-DOM-Level-1">DOM</jump>]</em> "Document Object Model (DOM) Level 1 Specification", Lauren Wood et al., 1 October 1998</li>
- <li><em>[<jump href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119</jump>]</em> "Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997</li>
+ <li><em>[<jump href="http://www.ietf.org/rfc/rfc2119.txt">RFC2119</jump>]</em> "Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997</li>
- <li><em>[<jump href="http://www.ietf.org/rfc/rfc2376.txt">RFC2376</jump>]</em> "XML Media Types", E. Whitehead, M. Murata, July 1998</li>
+ <li><em>[<jump href="http://www.ietf.org/rfc/rfc2376.txt">RFC2376</jump>]</em> "XML Media Types", E. Whitehead, M. Murata, July 1998</li>
- <li><em>[<jump href="http://www.ietf.org/rfc/rfc2396.txt">RFC2396</jump>]</em> "Uniform Resource Identifiers (URI): Generic Syntax", T. Berners-Lee, R. Fielding, L. Masinter, August 1998</li>
+ <li><em>[<jump href="http://www.ietf.org/rfc/rfc2396.txt">RFC2396</jump>]</em> "Uniform Resource Identifiers (URI): Generic Syntax", T. Berners-Lee, R. Fielding, L. Masinter, August 1998</li>
- <li><em>[<jump href="http://www.w3.org/TR/REC-xml">XML</jump>]</em> "Extensible Markup Language (XML) 1.0 Specification", T. Bray, J. Paoli, C. M. Sperberg-McQueen, 10 February 1998</li>
+ <li><em>[<jump href="http://www.w3.org/TR/REC-xml">XML</jump>]</em> "Extensible Markup Language (XML) 1.0 Specification", T. Bray, J. Paoli, C. M. Sperberg-McQueen, 10 February 1998</li>
- <li><em>[<jump href="http://www.w3.org/TR/REC-xml-names">XMLNAMES</jump>]</em> "Namespaces in XML", T. Bray, D. Hollander, A. Layman, 14 January 1999</li>
+ <li><em>[<jump href="http://www.w3.org/TR/REC-xml-names">XMLNAMES</jump>]</em> "Namespaces in XML", T. Bray, D. Hollander, A. Layman, 14 January 1999</li>
- <li><em>[<jump href="http://www.w3.org/TR/xslt">XSLT</jump>]</em> "XSL Transformations (XSLT) Specification Version 1.0", J. Clark, 16 November 1999</li>
+ <li><em>[<jump href="http://www.w3.org/TR/xslt">XSLT</jump>]</em> "XSL Transformations (XSLT) Specification Version 1.0", J. Clark, 16 November 1999</li>
- <li><em>[<jump href="http://www.megginson.com/SAX/">SAX</jump>]</em> "The Simple API for XML (Java implementation) version 1.0", D.Megginson, </li>
+ <li><em>[<jump href="http://www.megginson.com/SAX/">SAX</jump>]</em> "The Simple API for XML (Java implementation) version 1.0", D.Megginson, </li>
</ul>
</s2>
-
-<s2 title="Acknowledgements">
- <p>The following people have greatly contributed to the creation and design of this draft:</p>
- <ul>
- <li><p>Ricardo Rocha <<jump href="mailto:ricardo@apache.org">ricardo@apache.org</jump>></p></li>
- </ul>
-</s2>
-
</s2>