You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by cz...@apache.org on 2003/07/03 16:25:03 UTC
cvs commit: cocoon-site/src/documentation/content/xdocs/news archives.xml index.xml
cziegeler 2003/07/03 07:25:03
Modified: src/documentation/content/xdocs/community members.xml
mail-lists.xml mail-archives.xml
src/documentation/content/xdocs site.xml
src/documentation/content/xdocs/news archives.xml index.xml
Added: src/documentation/content/xdocs/link sites.xml xsl.xml
projects.xml dtd-schema.xml books.xml book.xml
hosting.xml index.xml in-the-press.xml
tips-guides.xml livesites.xml training.xml xml.xml
src/documentation/content/xdocs/community contrib.xml
Log:
Moved common docs to top level
Revision Changes Path
1.1 cocoon-site/src/documentation/content/xdocs/link/sites.xml
Index: sites.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Web Sites Providing Information About Cocoon</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="Web Sites Providing Information About Cocoon">
<ul>
<li><link href="http://wiki.cocoondev.org/">CocoDocoWiki</link>, the Cocoon
Documentation Wiki.</li>
<li><link href="http://outerthought.net/">http://outerthought.net/</link>
hosts several Cocoon-related resources.</li>
<li><link href="http://tecfa.unige.ch/guides/xml/cocoon-pointers.html">TECFA's little Cocoon Page</link><br/>
This page contains examples of using Cocoon, links to Cocoon/XSP documentation and general
XML/XSLT links.
</li>
<li><link href="http://ziegeler.bei.t-online.de/">The Ziegeler Community</link></li>
<li><link href="http://radio.weblogs.com/0107211/categories/cocoon/">Carsten Ziegeler's Cocoon Weblog</link></li>
<li><link href="http://radio.weblogs.com/0103021/">Matthew Langham's Radio Weblog</link></li>
<li><link href="http://needacake.blogspot.com/">Matthew Langham's VoicesInMyBlog</link></li>
<li><link href="http://www.cocooncenter.org/">Cocooncenter</link><br/>
A site completely dedicated to Cocoon, providing tutorials and
how-to articles written by Cocoon users. The articles - and other issues -
can be discussed in a forum.
</li>
<li><link href="http://www.cocoonhive.org/">CocoonHive.org</link><br/>
CocoonHive.org maintainings a catalog of articles on Best Practices,
Use Cases and Success Stories.
</li>
<li><link href="http://www.luminas.co.uk/technology/cocoon/url/">Cocoon-URL, a weekly summary of links posted to the cocoon mailing lists</link></li>
<li><link href="http://www.galatea.com/flashguides/index.html">Galatea FlashGuides(TM)</link></li>
<li><link href="http://durdo.miesto.sk/Cocoon2HowTo/index.html">Cocoon 2 How-To Pages</link> by Michal Durdina<br/>
Some tutorials, tips and hints for Cocoon 2 developers, e. g. how to build a database application
and how to use Cocoon with JBuilder.
</li>
<li><link href="http://www.luminas.co.uk/technology/cocoon/url/">Cocoon Lists Weekly Summary</link><br/>
Cocoon-URL is a weekly summary of interesting links posted to the mailing lists of the Cocoon project
</li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your site here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: Site:">tell us</link>.
Enter a meaningful title after the words "Link: Site:"
in the subject, provide a short summary of your site, and do not forget to
tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/xsl.xml
Index: xsl.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>XSL/XSLT Links</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="XSL/XSLT Links">
<ul>
<li><link href="http://www.w3.org/Style/XSL/">W3C XSL Standard</link></li>
<li><link href="http://www.w3.org/TR/xslt">W3C XSLT Standard</link></li>
<li><link href="http://www.xslt.com/">XSLT.com Resource Site</link></li>
<li><link href="http://xml.coverpages.org/xsl.html">OASIS XML Coverpages - XSL</link></li>
<li><link href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial</link></li>
<li><link href="http://www.nwalsh.com/docs/tutorials/xsl/">XSL Tutorial (Norman Walsh)</link></li>
<li><link href="http://www.dpawson.co.uk/xsl/xslfaq.html">XSL FAQ</link></li>
<li><link href="http://www.mulberrytech.com/xsl/">Mulberrytech XSL mailing list</link></li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your site/page here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: XSL:">tell us</link>.
Enter a meaningful title after the words "Link: XSL:"
in the subject, provide a short summary of your site/page, and do not forget
to tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
<p>
Please note that we are not trying to link to each and every site, rather
we provide a small collection of relevant starting points.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/projects.xml
Index: projects.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Cocoon-based and Cocoon-related Projects</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="Cocoon-based Projects">
<ul>
<li><link href="http://www.wyona.org/">Wyona CMS</link><br/>
Wyona CMS is an Open-Source Content Management and Publishing System written in 100% pure Java.
It is based on open standards such as XML ( DOM, SAX) and XSLT.
One of its core components is the pipeline processor Cocoon from the Apache Software Foundation.
</li>
<li><link href="http://opensource.yourdecor.ca/faq1/index.html">FAQ Project</link><br/>
A web-based, database driven that make use of JSP and XML and Cocoon.
</li>
<li><link href="http://www.sourcepole.com/sources/software/sp.xsl/">sp.xsl</link><br/>
Generate simple websites with XSL.
</li>
<li><link href="http://webeditor.sourceforge.net/">WebEditor WCMS</link><br/>
webEditor is a web application to manage the content of a news-based web site (you know Slashdot?).
It's based on Apache Cocoon and Apache/ApacheJServ/Tomcat as Web Server/Servlet platform.
</li>
<li><link href="http://chello.sourceforge.net/">Chello - A minimal Cocoon 2 application</link><br/>
Chello is an Open Source minimal Cocoon 2 application. It features project compilation using ANT,
unit testing with JUnit, functional testing with HTTPUnit, continuous integration process with CruiseControl,
documentation generation for Java code using javadoc and XSL Stylesheets using XSLDoc,
project documentation using Cocoon and automatic build of web archive file (WAR) for easy distribution.
</li>
<li><link href="http://sourceforge.net/projects/holometabolous/">Holometabolous - CMS, Profiling and App Suite</link><br/>
A content management, profiling and application suite built on top of software from the Apache foundation, most especially Cocoon, with a database back end.
The goal is to make the power of Java/SQL/XML easy to leverage 'out of the box.'
</li>
<li><link href="http://sourceforge.net/projects/xmlleague/">XMLLeague</link><br/>
Sports (soccer) league administration.
</li>
<li><link href="http://buglet.sourceforge.net/">Buglet - XML Bugtracking System</link><br/>
An xml-centric bug system implemented in Java as a servlet running on top of Cocoon/Tomcat.
Supports e-mail and web based submission of bugs.
Buglet offers a standardized form for the data associated with bugs.
</li>
<li>CocoBlog is a free weblogging software tool based on Apache Cocoon and
Apache Xindice. For more information see Ugo Cei's weblog at
<link href="http://www.beblogging.com/blog/">http://www.beblogging.com/blog/</link>
</li>
<li><link href="http://xreporter.cocoondev.org/">xReporter</link> is an Avalon/Cocoon-based database reporting application that makes use of XML report
definitions to produce HTML, CSV, Excel and PDF reports available across a web interface.</li>
</ul>
</s1>
<s1 title="Cocoon-related Projects">
<ul>
<li><link href="http://editxml.sourceforge.net/">EditXML - Managing XML files for Cocoon</link><br/>
Edit XML provides a servlet based solution for managing sets of XML files for XML based publishing systems like Cocoon.
</li>
<li><link href="http://pollo.sourceforge.net/">Pollo XML Editor (with Cocoon sitemap support)</link><br/>
Pollo lets you edit XML files. It's best suited for files which can be represented in a tree structure.
It comes with built-in support for Cocoon sitemap files, Ant build files and XML Schemas.
The editor has a colourful tree widget (not the default Swing one!), drag-and-drop support, unlimited undo, model-view design (open multiple views on the same file), ...
</li>
<li><link href="http://www.plenix.com/dbprism/">DBPrism XML Framework for Oracle DB</link><br/>
DBPrism is a servlet engine that works in two different modes: as a standalone servlet, or plugged into the Cocoon publishing framework.
In the first mode, DBPrism works like the PLSQL Cartridge of Oracle Web Server.
Plugged into the Cocoon framework, DBPrism works as a DB Producer, generating dynamic XML from a database.
</li>
<li><link href="http://jeuclid.sourceforge.net/">JEuclid - MathML Transformer for Cocoon</link><br/>
The project is a component for the Apache Cocoon project which converts MathML documents to GIF images or SVG.
</li>
<li><link href="http://exformula.d-haven.org/">ExFormula - XForms for Cocoon</link><br/>
ExFormula is an implementation of the XForms specification.
It allows you to define XML Models and Instances associated with it, to process dynamic forms based on an end markup.
</li>
<li><link href="http://jakarta.apache.org/poi/">POI - OLE2 File System (DOC, XLS, ...)</link><br/>
The POI project consists of APIs for manipulating various file formats based upon Microsoft's OLE 2 Compound Document format using pure Java.
There will soon be generators and serializers for Cocoon to read/write MS Office file formats.
</li>
<li><link href="http://opensource.bibop.it/bbp/xforge/index.html">X:Forge XML Framework</link><br/>
X:Forge is an XML Language whose main focus is in dynamic XML generation.
X:Forge tags are supposed to be included in XML documents for further processing.
The tool was designed as a replacement for XSP, an Apache technology originally used for dynamic generation of XML content in the Cocoon Project and slowly evolving into an Internet standard.
</li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your project here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: Project:">tell us</link>.
Enter a meaningful title after the words "Link: Project:"
in the subject, provide a short summary of your project, and do not forget
to tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/dtd-schema.xml
Index: dtd-schema.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>DTD/XML Schema Links</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="DTD Links">
<ul>
<li><link href="http://www.w3schools.com/dtd/">W3Schools DTD Tutorial</link></li>
<li><link href="http://ctdp.tripod.com/independent/web/dtd/">Document Type Definition (DTD) Introduction</link></li>
<li><link href="http://java.sun.com/webservices/docs/ea2/tutorial/doc/JAXPSAX7.html">Creating a Document Type Definition (DTD)</link> (Java Web Services Tutorial)</li>
<li><link href="http://aips2.nrao.edu/docs/reference/Coding/node41.html">Document Type Definition</link> (from the AIPS++ Programming Manual)</li>
</ul>
</s1>
<s1 title="XML Schema Links">
<ul>
<li><link href="http://www.w3.org/XML/Schema">W3C XML Schema</link></li>
<li><link href="http://www.w3.org/TR/xmlschema-0/">W3C XML Schema Part 0: Primer</link></li>
<li><link href="http://www.w3.org/TR/xmlschema-1/">W3C XML Schema Part 1: Structures</link></li>
<li><link href="http://www.w3.org/TR/xmlschema-2/">W3C XML Schema Part 2: Datatypes</link></li>
<li><link href="http://www.oasis-open.org/cover/schemas.html">OASIS XML Coverpages - XML Schemas</link></li>
<li><link href="http://www.ibiblio.org/xml/slides/xmlone/london2002/schemas/">Mastering XML Schemas</link></li>
<li><link href="http://xml.com/pub/a/2001/12/12/schemacompare.html">Comparing XML Schema Languages</link></li>
<li><link href="http://www.w3schools.com/schema/">W3Schools XML Schema Tutorial</link></li>
<li><link href="http://www.xml.com/pub/a/2000/11/29/schemas/part1.html">Using W3C XML Schema</link></li>
<li><link href="http://www.alphaworks.ibm.com/tech/xmlsqc">IBM AlphaWorks XML Schema Quality Checker</link></li>
<li><link href="http://www.xfront.com/xml-schema.html">XML Schema Tutorial</link> (.zip download, must accept license first)</li>
<li><link href="http://www.xml.com/pub/rg/Schema_Tutorials">XML.com Schema Tutorials</link></li>
</ul>
</s1>
<s1 title="Links to Other Types of Schema">
<ul>
<li><link href="http://www.oasis-open.org/committees/relax-ng/">OASIS Technical Committee: RELAX NG</link></li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your site/page here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: Schema:">tell us</link>.
Enter a meaningful title after the words "Link: Schema:"
in the subject, provide a short summary of the site/page, and do not forget
to tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
<p>
Please note that we are not trying to link to each and every site, rather
we provide a small collection of relevant starting points.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/books.xml
Index: books.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Books about Cocoon</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="Books about Cocoon">
<p>
These are books about Cocoon, Version 2.x, which are already available or planned.
</p>
<ul>
<li><link href="http://www.newriders.com/books/product.asp?product_id={C3C05052-BE3B-4E06-A60A-13FB40AF58F6}">Cocoon: Building XML Applications</link> (Carsten Ziegeler, Matthew Langham)<br/>
<strong>Availability:</strong> July 2002<br/>
<strong>Paperback:</strong> 504 pages<br/>
<strong>Publisher:</strong> New Riders Publishing<br/>
<strong>ISBN:</strong> 0735712352<br/>
Please note that you can download several <link href="http://www.newriders.com/books/product.asp?product_id={C3C05052-BE3B-4E06-A60A-13FB40AF58F6}" >free chapters</link> at the New Riders web site.
</li>
<li><link href="http://www.amazon.com/exec/obidos/ASIN/0672322579/">Cocoon Developer's Handbook</link> (Jeremy Aston, Lajos Moczar)<br/>
<strong>Availability:</strong> September 2002<br/>
<strong>Paperback:</strong> 500 pages<br/>
<strong>Publisher:</strong> Sams<br/>
<strong>ISBN:</strong> 0672322579
</li>
<li><link href="http://www.amazon.com/exec/obidos/ASIN/0782141315/">Cocoon 2 Programming: Web Publishing with XML and Java</link> (Bill Brogden, Conrad D'Cruz, Mark Gaither)<br/>
<strong>Availability:</strong> October 2002<br/>
<strong>Paperback:</strong> 368 pages<br/>
<strong>Publisher:</strong> Sybex<br/>
<strong>ISBN:</strong> 0782141315
</li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your book here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: Book:">tell us</link>.
Enter the title after the words "Link: Book:" in the subject, and
provide a short summary of your book. Do not forget to tell us the URL if
possible (preferably direct to the publisher, rather than any particular
bookshop).
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/book.xml
Index: book.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//APACHE//DTD Cocoon Documentation Book V1.0//EN" "book-cocoon-v10.dtd">
<book software="Apache Cocoon"
title="Apache Cocoon Links"
copyright="@year@ The Apache Software Foundation">
<menu label="Navigation">
<menu-item label="Main" href="../index.html"/>
</menu>
<menu label="Overview">
<menu-item label="Links Overview" href="index.html"/>
</menu>
<menu label="External Resources">
<menu-item label="Books" href="books.html"/>
<menu-item label="Articles" href="in-the-press.html"/>
<menu-item label="Tips and Guides" href="tips-guides.html"/>
<menu-item label="Training" href="training.html"/>
</menu>
<menu label="External Sites">
<menu-item label="Info Sites" href="sites.html"/>
<menu-item label="Projects" href="projects.html"/>
<menu-item label="Live Sites" href="livesites.html"/>
<menu-item label="Cocoon Hosting" href="hosting.html"/>
</menu>
<menu label="Related Topics">
<menu-item label="XML" href="xml.html"/>
<menu-item label="XSL/XSLT" href="xsl.html"/>
<menu-item label="DTD/Schema" href="dtd-schema.html"/>
</menu>
</book>
1.1 cocoon-site/src/documentation/content/xdocs/link/hosting.xml
Index: hosting.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Cocoon Hosting</title>
<authors>
<person name="Robin Green" email="greenrd@hotmail.com"/>
</authors>
</header>
<body>
<s1 title="Cocoon Hosting">
<p>
Here is a list of some sites that provide Apache Cocoon web hosting
(in no particular order). Version information may not be up-to-date
on this list, so always check with the site itself to make sure. Of course,
most are commercial providers, yet some have free services.
</p>
<ul>
<li><link href="http://www.aoindustries.com/">AO Industries</link> - Cocoon 1.8</li>
<li><link href="http://webartists.net/webhosting.html">Webartists</link> (German)</li>
<li><link href="http://www.capital-internet.net/">Capital Internet</link> - Cocoon 2 (pre-2.0 support will still be available)</li>
<li><link href="http://dev.startcom.org/">MediaHost Developer Accounts</link> - from Cocoon 1.8.2 up to latest Cocoon 2.1</li>
<li><link href="http://www.va.com.au/">Virtual Artists Pty Ltd</link> - Cocoon 1 or Cocoon 2</li>
<li><link href="http://www.hub.org/">Hub.Org Networking Services</link> - Cocoon 2 or Cocoon 1</li>
<li><link href="http://www.dyanet.com/">Dyanet</link> - Cocoon 2</li>
<li><link href="http://www.mmaweb.net/">Motivational Marketing Associates, Inc</link> - Cocoon 1.7.4</li>
<li><link href="http://www.webappcabaret.com">WebAppCabaret</link> - Cocoon 2.0.2</li>
<li><link href="http://www.wisernet.com">Wiserlabz</link> - Cocoon 2.0.3 for commercial projects.</li>
<li><link href="http://www.hebergement-pro.com">Hebergement-pro</link> - Cocoon 2.0.2, including cheap starter pack.</li>
<li><link href="http://rimuhosting.com">RimuHosting</link> - Java Hosting Specialists, latest Cocoon on request.</li>
</ul>
<p><strong>Free ...</strong></p>
<ul>
<li><link href="http://www.wiserlabz.com">Wiserlabz</link> - free Cocoon, Tomcat and Apache developer accounts.</li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your site here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link Hosting:">tell us</link>.
Enter a meaningful title after the words "Link Hosting:"
in the subject, provide a short summary of your site and do not forget
to tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
<p>
You must have Cocoon up and running and be accepting application forms.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/index.xml
Index: index.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Cocoon Links Overview</title>
<subtitle>Overview</subtitle>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="Cocoon Links Overview">
<p>
There is a wealth of information about Cocoon from external sources.
This is a collection of links to some of them.
</p>
<p>
Come back often ... this collection is being updated regularly via the
<code>cocoon-users</code> mailing list.
</p>
<p>The actual link category pages are available from the side-panel.
</p>
</s1>
<s1 title="How to get listed">
<p>
Find out in which section of the Cocoon Links your site/page fits,
go there and use the email link at the bottom of the corresponding section.
Enter a meaningful title after the required words in the subject,
provide a short summary of your site/page, and do not forget to tell us
the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/in-the-press.xml
Index: in-the-press.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Articles about Cocoon: What they say about Cocoon</title>
<authors>
<person name="Luca Morandini" email="lmorandini@ieee.org"/>
<person name="Stephan Michels" email="stephan@apache.org"/>
</authors>
</header>
<body>
<s1 title="English articles">
<ul>
<li>
<link href="http://www.xml.com/pub/a/2003/04/23/cocoon-magazine.html">
Online Magazines with Apache Cocoon
</link>
<br/>
An article about aggregation of news with RSS.
</li>
<li>
<link href="http://webservices.xml.com/pub/a/ws/2003/03/18/cocoon.html">
Creating SOAP Services with Cocoon
</link>
<br/>
An article about building webservices with Cocoon.
</li>
<li>
<link href="http://webservices.xml.com/pub/a/ws/2003/01/29/cocoon-xforms.html">
XML Forms, Web Services and Apache Cocoon
</link>
<br/>
Using XML Forms with Cocoon.
</li>
<li>
<link href="http://www.xml.com/pub/a/2003/01/22/cocoon-excel.html">
Excel Reports with Apache Cocoon and POI
</link>
<br/>
Creating Excel reports.
</li>
<li>
<link href="http://www.xml.com/pub/a/2002/02/13/cocoon2.html">
Introducing Cocoon 2.0
</link>
<br/>
An article by Stefano Mazzocchi on xml.com... need we say more to make you read it ?
</li>
<li>
<link href="http://www.sys-con.com/java/articleprint.cfm?id=1480">
Spread your Wings with Cocoon, David Rosenstrauch, Java Developer's Journal, Volume 07, Issue 06
</link>
<br/>
The title says it all...
</li>
<li>
<link href="http://www.webreference.com/xml/column52/">
Generating Web content with Cocoon
</link>
<br/>
Introductory article about Cocoon pipelines.
</li>
<li>
<link href="http://www.webservices.org/index.php/article/articleview/613/1/24/">
Portal Syndication with Web services and Cocoon
</link>
<br/>
Good case-study
</li>
<li>
<link href="http://www.javaworld.com/javaworld/jw-09-2002/jw-0920-cocoon.html">
Transform data into Web applications with Cocoon, Lajos Moczar, JavaWorld, September 2002
</link>
<br/>
Emphasis on the Java parts of Cocoon (XSP and Actions, basically)
</li>
<li>
<link href="http://www.xml.com/pub/a/2002/07/10/cocoon2.html">
Getting Started With Cocoon 2
</link>
<br/>
How to get started with Cocoon.
</li>
<li>
<link href="http://www.webreference.com/xml/column52/">
Generating Web content with Cocoon
</link>
<br/>
Basic article to dive into Cocon.
</li>
<li>
<link href="http://www.javaworld.com/javaworld/jw-02-2001/jw-0209-xmlj2ee_p.html">
Add XML to your J2EE applications, Eoin Lane, JavaWorld, February 2001
</link>
<br/>
Comprehensive article about integrating Cocoon and a J2EE framework.
</li>
<li>
<link href="http://www.sdmagazine.com/articles/2001/0105/">
Is open source for you ?, Rick Wayne, Software Development, May 2001
</link>
<br/>
A worthy mention of Cocoon
</li>
<li>
<link href="http://www.sdmagazine.com/products/prev_reviews.html">
Products review, Software Development, December 2001,
</link>
<br/>
Little review of Cocoon 2.0
</li>
<li>
<link href="http://www.sdmagazine.com/articles/2001/0106/">
The Apache XML Project: How to Get Read All Over, Rick Wayne, Software Development, June 2001,
</link>
<br/>
Nice article about Cocoon 1
</li>
<li>
<link href="http://www.fawcette.com/archives/premier/mgznarch/javapro/2000/08aug00/kj0008/kj0008.asp">
A Better Way for Web Development, Kevin Jones, XML Magazine, Fall 2000
</link>
<br/>
Another article about Cocoon 1
</li>
</ul>
</s1>
<s1 title="German articles">
<ul>
<li>
<link href="http://www.computerwoche.de/index.cfm?pageid=267&type=ArtikelDetail&id=80106336&cfid=142863&cftoken=29262623&nr=1">
Publishing mit freier Apache-Software, COMPUTERWOCHE Nr. 06 vom 08.02.2002 (Langham/Ziegeler)
</link>
</li>
<li>
Cocoon - aber sicher, XML Magazin & Web Services, Issue 3, 2002 (Langham/Ziegeler)
<br/>
The article introduces the reader to the authentication components in Cocoon and
how they integrate into the central sitemap.
</li>
<li>
Ante Portas! XML Portale mit dem Open Source Projekt Cocoon, XML Magazin & Web Services, Issue 3, 2002 (Langham/Ziegeler)
<br/>
The article shows how the Cocoon portal components can be used to build XML portals.
</li>
</ul>
</s1>
<s1 title="Italian articles">
<ul>
<li>
<link href="http://www.latoserver.it/cocoon/install_c2/">
Installazione di Tomcat 4 e Cocoon 2 su Mac OS X e Linux Debian
</link>
<br/>
Installazione di Cocoon 2
</li>
<li>
<link href="http://www.latoserver.it/cocoon/install_c1/">
Installazione di Tomcat e Cocoon
</link>
<br/>
Installazione di Cocoon 1
</li>
<li>
<link href="http://www.latoserver.it/cocoon/sitemg/">
Gestione di un sito con XML e Cocoon
</link>
<br/>
Introduttorio, con Cocoon 1
</li>
<li>
<link href="http://www.latoserver.it/cocoon/sm/">
Intervista a Stefano Mazzocchi
</link>
<br/>
Intervista datata (Febbraio 2001), ma sempre interessante
</li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your book here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: Article:">tell us</link>.
Enter the title after the words "Link: Article:" in the subject, and
provide the title and publications of your article. Do not forget to tell us the URL if
possible.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/tips-guides.xml
Index: tips-guides.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Cocoon Tips and Guides</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="Cocoon Tips and Guides (English)">
<p>
Here you can find various tips, tutorials and guides on specific cocoon-related topics spread all over the internet.
Unless otherwise explicitly noted, all documents refer to the 2.x series of Cocoon.
</p>
<ul>
<li>
<link href="http://www-105.ibm.com/developerworks/education.nsf/xml-onlinecourse-bytitle/83F66813F7FFD61486256B74006EB648?OpenDocument">
Introduction to Cocoon 2
</link>
<br/>
Introduction to Cocoon 2 is a tutorial by Leigh Dodds,
published on IBM developerWorks site.
</li>
<li>
<link href="http://www-105.ibm.com/developerworks/education.nsf/xml-onlinecourse-bytitle/14DFAEE91D8BB1EF86256BA300662FAF?OpenDocument">
Working with XML Server Pages in Apache Cocoon 2
</link>
<br/>
Working with XML Server Pages in Apache Cocoon 2 is another tutorial by Leigh Dodds,
published on IBM developerWorks site.
</li>
<li><link href="http://ziegeler.bei.t-online.de/tecart.html">Introduction to Cocoon authentication (C. Ziegeler)</link></li>
<li><link href="http://radio.weblogs.com/0107211/stories/2002/04/26/theNewCocoonSourceResolving.html">Differences between Cocoon and Avalon Excalibur Source Resolving (Ziegeler)</link></li>
<li><link href="http://radio.weblogs.com/0103021/stories/2002/02/14/cocoonPortalFirstLook.html">Cocoon portal - first look (Langham)</link></li>
<li><link href="http://radio.weblogs.com/0103021/stories/2002/02/28/usingTheSunriseComponents.html">Using the sunRise components (Langham)</link></li>
<li><link href="http://www.galatea.com/flashguides/cocoon-tips-2.xml">Galatea FlashGuide: Cocoon2 Tips and Tricks</link> by Lajos Moczar<br/>
This FlashGuideTM provides various tips and tricks for Cocoon2, e. g.
database pooling, running multiple instances of Cocoon,
and removing 'cocoon' from your URL base.
</li>
<li><link href="http://durdo.miesto.sk/Cocoon2HowTo/index.html">Cocoon 2 How To Pages</link></li>
<li><link href="http://www.suranyami.com/intro.html">XSP Tutorial</link> by David Perry<br/>
A tutorial describing what XSP pages are and how to create them.
</li>
<li><link href="http://www.jboss.org/online-manual/HTML/ch14s07.html">Deploying Cocoon 2 in JBoss</link><br/>
An installation guide for Cocoon with the JBoss application server.
</li>
</ul>
</s1>
<s1 title="Cocoon Tips and Guides (German)">
<p>
Here you can find various tips, tutorials and guides on specific cocoon-related topics in german.
Unless otherwise explicitly noted, all documents refer to the 2.x series of Cocoon.
</p>
<ul>
<li><link href="http://entwickler.com/itr/online_artikel/show.php3?id=154&nodeid=97">Cocoon Introduction Part 1 (Langham/Ziegeler)</link></li>
<li><link href="http://entwickler.com/itr/online_artikel/show.php3?id=155&nodeid=97">Cocoon Introduction Part 2 (Langham/Ziegeler)</link></li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your page here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: Guide:">tell us</link>.
Enter a meaningful title after the words "Link: Guide:"
in the subject, provide a short summary of your page, and do not forget
to tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/livesites.xml
Index: livesites.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Live Sites Powered by Apache Cocoon 2.1</title>
<authors>
<person name="Cocoon Developers" email="dev@cocoon.apache.org"/>
</authors>
</header>
<body>
<!--<li><link href=""></link></li>-->
<s1 title="Live Sites powered by Apache Cocoon 2.1">
<p>
Here are some web sites that are proudly powered by Cocoon 2.1
(only ordered by Cocoon version):
</p>
<s2 title="Cocoon 2.1m3-dev">
<ul>
<li><link href="http://www.adolos.com/">Adolos</link></li>
</ul>
</s2>
<s2 title="Cocoon 2.1m2-dev">
<ul>
<li><link href="http://www.iniva.org/">The Institute of International Visual Arts</link></li>
<li><link href="http://www.mammakarzinom.de">Disease Management Mammakarzinom</link></li>
</ul>
</s2>
<s2 title="Cocoon 2.1-dev">
<ul>
<li><link href="http://cupva.cbim.it/">Servizio Prima Disponibilità</link></li>
<li><link href="http://dir.salon.com/">Salon Directory</link></li>
<li><link href="http://www.boonetakeout.com/">Boone Takeout</link></li>
<li><link href="http://www.datadreamers.com/">Data Dreamers</link></li>
<li><link href="http://www.sac-piz-sol.ch/">SAC Sektion Piz Sol</link></li>
<li><link href="http://www.ormaz.it">Ormaz s.r.l.</link></li>
</ul>
</s2>
<p>
Of course, all of the websites listed on the Apache Forrest
<link href="http://xml.apache.org/forrest/live-sites.html">Live sites</link>
page are also essentially powered by Cocoon.
</p>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your site here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link Livesites:">tell us</link>.
Enter a meaningful title and the version of Cocoon after the words "Link Livesites:" in the
subject, provide a short summary of your site, and do not forget to tell us the URL. You could
also follow the <link href="../community/contrib.html">Contributing</link> page to make it easier for
everyone.
</p>
<p>We would like to see this list grow bigger every day :-)</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/training.xml
Index: training.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Cocoon Training</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="Cocoon Training">
<ul>
<li><link href="http://www.galatea.com/training/index.html">Galatea Information Strategies</link><br/>
They have two classes now available: Cocoon Fundamentals and Advanced Cocoon.
Both courses are two days each and are offered in Denver, Colorado.
It is also possible to arrange on-site training if there are sufficient participants.
</li>
<li><link href="http://www.s-und-n.de/sunshine/services-training-cocoonschulungen_english">S&N AG</link><br/>
S&N offers Cocoon training. Two courses are available -
"Introducing Cocoon" (3 days) for beginners and "Unraveling Cocoon" for
developers (2 days). The courses are available in English or German.
It is also possible to arrange on-site training.
</li>
<li><link href="http://www.anyware-tech.com">Anyware Technologies</link><br/>
Anyware Technologies offers <link href="http://www.anyware-tech.com/french/sce_training.html">Cocoon
training</link> in France. Course are organized in two classes (3 day introduction and 2 day advanced),
but can be mixed with our other XML and Java training material to meet specific needs.
Courses are held in French and can be on-site.
</li>
<li><link href="http://www.oio.de/">Orientation in Objects</link><br/>
You can learn how to develop web applications using Cocoon and XSPs in a three
day training course. Courses will take place every 2 months in Mannheim,
Germany.
See <link href="http://www.oio.de/seminar/xml/cocoon-schulung.htm">course
description</link>. We also offer on-site training in English.
</li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your site here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: Training:">tell us</link>.
Enter a meaningful title after the words "Link: Training:"
in the subject, provide a short summary of your site, and do not forget
to tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
</s1>
</body>
</document>
1.1 cocoon-site/src/documentation/content/xdocs/link/xml.xml
Index: xml.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>XML Links</title>
<authors>
<person name="Andreas Hochsteger" email="e9625392@student.tuwien.ac.at"/>
</authors>
</header>
<body>
<s1 title="XML Links">
<ul>
<li><link href="http://www.w3.org/XML/">W3C XML Standard</link></li>
<li><link href="http://dmoz.org/Computers/Data_Formats/Markup_Languages/XML/">XML Links at DMOZ</link></li>
<li><link href="http://www.xml.com/">XML.com </link></li>
<li><link href="http://www.xml.org/">XML.org - The XML Industry Portal</link></li>
<li><link href="http://www.oasis-open.org/cover/sgml-xml.html">OASIS XML Cover Pages</link></li>
<li><link href="http://www.ucc.ie/xml/">XML FAQ</link></li>
<li><link href="http://www-106.ibm.com/developerworks/xml/">IBM DeveloperWorks XML Zone</link></li>
</ul>
</s1>
<s1 title="How to get listed">
<p>
If you do not find your site/page here, make sure you
<link href="mailto:users@cocoon.apache.org?subject=Link: XML:">tell us</link>.
Enter a meaningful title after the words "Link: XML:"
in the subject, provide a short summary of your site/page, and do not forget
to tell us the URL.
You could also follow the <link href="../community/contrib.html">Contributing</link>
page to make it easier for everyone.
</p>
<p>
Please note that we are not trying to link to each and every site, rather
we provide a small collection of relevant starting points.
</p>
</s1>
</body>
</document>
1.2 +1 -2 cocoon-site/src/documentation/content/xdocs/community/members.xml
Index: members.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/community/members.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- members.xml 16 Jun 2003 11:02:10 -0000 1.1
+++ members.xml 3 Jul 2003 14:25:02 -0000 1.2
@@ -1,6 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
-"document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
<document>
<header>
<title>The Cocoon Community</title>
1.2 +2 -2 cocoon-site/src/documentation/content/xdocs/community/mail-lists.xml
Index: mail-lists.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/community/mail-lists.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mail-lists.xml 3 Jul 2003 09:46:27 -0000 1.1
+++ mail-lists.xml 3 Jul 2003 14:25:02 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
<document>
<header>
@@ -22,7 +22,7 @@
<p><strong>IMPORTANT:</strong> Careful postings please.
These are high-volume lists, so we all needs ways to help us all
work smarter.
- See tips for <link href="http://cocoon.apache.org/2.1/contrib.html#tips">Contributing</link>
+ See tips for <link href="contrib.html#tips">Contributing</link>
</p>
</section>
1.2 +1 -1 cocoon-site/src/documentation/content/xdocs/community/mail-archives.xml
Index: mail-archives.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/community/mail-archives.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mail-archives.xml 3 Jul 2003 09:46:27 -0000 1.1
+++ mail-archives.xml 3 Jul 2003 14:25:02 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "dtd/document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
<document>
<header>
1.1 cocoon-site/src/documentation/content/xdocs/community/contrib.xml
Index: contrib.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "document-v10.dtd">
<document>
<header>
<title>Contribution to Apache Cocoon</title>
<authors>
<person name="Robin Green" email="greenrd@hotmail.com"/>
<person name="Stefano Mazzocchi" email="stefano@apache.org"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>
The Apache Cocoon Project is an <link href="http://www.opensource.org/">Open Source</link>
volunteer project under the auspices of the
<link href="http://www.apache.org/">Apache Software Foundation (ASF)</link>,
and, in harmony with the Apache webserver itself, it is released under
a very open license.
This means there are many 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
donations (money, time, publicity, hardware, software, conference
presentations, speeches, etc...).
</p>
<p>
To begin with, we suggest you to subscribe to the
<link href="mail-lists.html">Cocoon mailing lists</link>
(follow the link for information on how to subscribe and to access the mail
list archives). Listen-in for a while, to hear how others make contibutions.
</p>
<p>You can get your local working copy of the
<link href="http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/">latest and
greatest code</link> (which you find in the cocoon-2.1 module in
the cvs.apache.org CVS code repository, or from the
<link href="http://xml.apache.org/cocoon/mirror.cgi#nightly">CVS snapshots</link>).
Review the <link href="http://cocoon.apache.org/2.1/todo.html">todo</link> list, choose a task
(or perhaps you have noticed something that needs patching). Make the
changes, do the testing, generate a patch, if you need then discuss it on
the cocoon-dev mailing list, and add the patch to Bugzilla.
(Do not worry - the process is easy and explained below.)
</p>
<p>
Document writers are usually the most wanted people so if
you like to help but you're not familiar with the innermost technical details, don't worry:
we have work for you!
</p>
</s1>
<s1 title="Help Wanted Here">
<p>
The rest of this document is mainly about
contributing new or improved code and/or documentation, but we would also be glad to have
extra help in any of the following areas:
</p>
<ul>
<li>Answering questions on the <code>cocoon-users</code> mailing list - there is often a problem of
having too many questioners and not enough experts to respond to all the questions.</li>
<li>Testing Cocoon (especially its less-frequently-used features) on various configurations
and reporting back.</li>
<li>Debugging - producing reproduceable test cases and/or finding causes of bugs. Some known bugs are informally listed on
<link href="http://cocoon.apache.org/2.1/todo.html">To Do</link>, and some are recorded in Bugzilla
(see <link href="#procedure">explanation below</link>).</li>
<li>Specifying/analysing/designing new features for Cocoon - and beyond. (If you wish to get involved
with this, please join <code>dev@cocoon.apache.org</code>
(you may also want to join <code>xsp-dev@xml.apache.org</code>), install and try out Cocoon
and read some of the <link href="mail-lists.html">mail archives</link>.
You should have a strong "fluency" in XML technologies, Java and a basic understanding of
the Cocoon architecture - don't just say "it should have XYZ" without reading anything first -
because chances are, someone's already thought of that feature!)</li>
<li>Packaging easy-to-install packages (such as RPMs) for the myriad of possible configurations out
there. (The Cocoon project does not maintain anything but the basic <code>.zip</code> and
<code>.tar.gz</code> packages, but anyone is welcome to build their own specific packages and
announce them on <code>cocoon-users</code>)</li>
<li>... and there is just one other thing - don't forget to tell everyone who asks, how great Cocoon is! ;-)
The more people that know about and start to use Cocoon, the larger the pool of
potential contributors there will be
- so, please, help us by placing the Cocoon logo somewhere in your
site to indicate that you are using and supporting the Cocoon Project.
</li>
</ul>
<p>
Thank you very much.
</p>
</s1>
<s1 title="Contributions of Code and Documentation">
<p>We are starting to use an informal system for accepting contributions to Cocoon.
The process varies depending on whether the contribution is a modification (i.e. patch)
or a fairly standalone item, and whether you have commit access (committers have been
granted access by a vote of confidence, so they are assumed to be trustworthy enough
to make changes directly in CVS. If you submit many good patches, you may be
nominated as a committer yourself!)</p>
<p>If your contribution requires changing more than a few lines of Cocoon (code or
documentation), then it counts as a <strong>patch</strong>. If you have a patch and
would like to see it incorporated into the Cocoon distribution, take note of the Licensing
Requirements listed below, and then read the section
<link href="#procedure">Procedure for Raising Development Issues</link>
</p>
<!--
<p>Otherwise (that is, if it does not require patching or you are not particularly interested in
having it included in the main distribution), your code and/or
documentation can be listed on the
<link href="3rdparty.html">Third-Party Contributions</link> page.
The rationale for this split is that core patches may fix important issues, and may
require timely attention if they are not to go
out-of-date and become useless, but other contributions can simply be downloaded and
applied by users who wish to use them.
</p>
-->
<p>A typical contribution (not a patch) may go through the following stages:</p>
<ol>
<li>Posted to cocoon-users with a URL to download it from.</li>
<!-- <li>Listed on 3rdparty.html by a maintainer. [No requirements, other than relevance (at the moment).]</li> -->
<li>Inclusion into the <code>contrib</code> directory,
which is for 3rd-party contributions that have been tested, but are not necessarily
mature enough or general enough for the main distribution. [Must be tested at least as
specified below. See also Licensing Requirements below.]</li>
<li>Inclusion into the main distribution. [Committers must be confident that it should work properly in
most/all environments, it must be documented as appropriate, and it must be considered sufficiently
useful and general to go into Cocoon. See also Licensing Requirements below].</li>
</ol>
<s2 title="Testing Requirements for Cocoon Contrib and Distribution">
<p>All new code should be tested under at least the following servlet engines:</p>
<ul>
<li>Apache Tomcat 3.2.2</li>
</ul>
<p>It should also be tested on the following platforms:</p>
<ul>
<li>A Windows operating system</li>
<li>A UNIX-type operating system</li>
<li>At least JDK version 1.3.x</li>
</ul>
<p>And obviously, it should be tested against the current CVS snapshot of Cocoon!</p>
<p>This testing is designed to iron out the most common kinds of incompatibility
problems (Servlet >2.2 requirements; platform-dependent assumptions; JDK >1.2 code).
These requirements are, of course, open to review and discussion. Note that
the contributor is not required to do the testing - indeed it is probably better
if someone else tests it, because the contributor might be tempted to do less
than thorough testing!</p>
</s2>
<s2 title="Documentation Requirements for Cocoon Distribution">
<p>All new features (processor, logicsheets, config options etc.) should be documented
appropriately (in XML or in <code>cocoon.xconf</code> in the case of config options).</p>
<p>Use something like <code>xdocs/contrib.xml</code> as a rough guide, add
the new page(s) to <code>xdocs/book.xml</code> to create the menu-link
and type <code>build.sh docs</code> or <code>build.bat docs</code> to test the
documentation build.
</p>
</s2>
<s2 title="Licensing Requirements for the Cocoon Distribution">
<p>To avoid legal problems, the Apache Project Management Committee (PMC) have agreed on
a policy for under what licensing code can be accepted into Apache projects:</p>
<ul>
<li>Source code files must be under the Apache license and must have copyright assigned to
the Apache Software Foundation.</li>
<li>Jar files need only be released under a license that permits free redistribution
and does not cover new files added to the jar/library (so the GPL and LGPL are not allowed,
but MPL and Apache licenses are, for example).</li>
</ul>
<p><strong>By submitting a patch, you signify your understanding and acceptance of these
conditions</strong> - like most open source projects,
we do not have the resources nor the inclination to obtain signed statements from all
contributors!</p>
<p><strong>Note:</strong> Since the <code>contrib/</code> directory of Cocoon CVS contains
third-party. completely optional extensions, one of the above requirements is relaxed.
Code in the contrib directory does not have to have its copyright assigned to the ASF
- but it must still be released under the Apache license.</p>
</s2>
</s1>
<anchor id="cvshowto"/>
<s1 title="CVS Usage Precis">
<p>An overview of how to use CVS to participate in Cocoon development.
Do not be afraid - you cannot accidently destroy the actual code repository,
because you are working with a local copy as an anonymous user. Therefore,
you do not have the system permissions to change anything. You can only
update your local repository and compare your revisions with the real
repository.
</p>
<p>
(Further general CVS usage information is at
<link href="http://www.cvshome.org/">www.cvshome.org</link> and your local
<code>info cvs</code> pages or <code>man cvs</code> pages or user
documentation.)
</p>
<p>
Let us lead by example. We will show you how to establish your local
repository, how to keep it up-to-date, and how to generate the differences
to create a patch. (The commands are for Linux.)
</p>
<s2 title="How to Establish your Local Repository">
<p>
This will checkout the current copy of the master cvs repository and
download it to your local disk. It will create a sub-directory called
<code>cocoon-2.1</code>
</p>
<ol>
<li><code>cd /usr/local/cvs</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login</code></li>
<li>... use this password: <code>anoncvs</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic checkout cocoon-2.1</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic logout</code></li>
<li><code>cd cocoon-2.1</code></li>
</ol>
<p>
You now have the HEAD branch of the current development cvs repository
for Cocoon on your local system. Go ahead and build and deploy as
usual. Make some changes, re-build, and see the effect.
</p>
</s2>
<s2 title="How to Keep it Up-to-date">
<p>
Every so often you should synchronise your local copy with the master
repository. Note that this definitely does not mean that your changes
will be applied to the master. Exactly the opposite will happen - updates
from the remote master version are merged into your local repository.
New items are automatically added to yours, and changed ones are refreshed.
If someone else happened to have submitted patches for the same files while
you were away, then changes will be merged with your copy and you will be
warned of any conflicts. Easy and automatic ...
</p>
<ol>
<li><code>cd /usr/local/cvs</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic update -d -P cocoon-2.1</code></li>
<li><strong>... pay attention to the update messages</strong></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic logout</code></li>
</ol>
</s2>
<s2 title="How to Generate Differences">
<p>
To contribute your modifications, you need to produce a plain-text file
containing the differences between the master copy and yours. You will
submit this to Bugzilla along with an explanation of why it is required,
and perhaps discuss it on the
<code>cocoon-dev</code> mailing list. One of the authorised
maintainers of the repository will review the patch and then apply it to the
relevant branch.
</p>
<p>
We will assume that you are adding some tips to this document
<code>xdocs/contrib.xml</code>
</p>
<ol>
<li>Make the desired changes in your local repository, build, test it
thoroughly</li>
<li><code>cd /usr/local/cvs/cocoon-2.1/xdocs</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login</code></li>
<li><code>cvs diff -u contrib.xml > $WORK/cocoon/contrib.xml.diff</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic logout</code></li>
</ol>
</s2>
<s2 title="How to get other CVS branches">
<p>OK that got the HEAD branch of CVS into your local working copy.
If you want some other branch, then find the relevant branch name
from ViewCVS
<link href="http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/">http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/</link> (see the Tags list at the bottom).
Then follow the same checkout procedure described above, using this ...
</p>
<ul>
<li><code>cd /usr/local/cvs/cocoon_some_branch</code></li>
<li><code>cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic checkout cocoon-2.0</code></li>
</ul>
</s2>
</s1>
<anchor id="ssh"/>
<s1 title="CVS Committer with Secure Shell access">
<p>After a developer has consistently provided contributions (code,
documentation and discussion), then the rest of the cocoon-dev community
may vote to grant this developer commit access to CVS.
</p>
<p>You will need secure access to the repository to be able to commit
patches. Here are some resources that help to get your machine configured
to use the repository over SSH.
</p>
<ul>
<li><link href="http://cvsbook.red-bean.com/">The CVS Book</link></li>
<li><link href="http://www.cvshome.org/">www.cvshome.org</link></li>
<li><link href="http://jakarta.apache.org/site/cvsindex.html">Jakarta
Guide: CVS Repository</link>
- See the bottom of the page for links to tips for UNIX and Windows.
Even if you are on UNIX, the Windows page will also help.</li>
</ul>
</s1>
<anchor id="procedure"/>
<s1 title="Procedure for Raising Development Issues">
<p>
There are two methods for discussing development and submitting patches.
So that everyone can be productive, it is important to know which method
is appropriate for a certain situation and how to go about it without
confusion. This section explains when to use the
<code>cocoon-dev</code> <link href="mail-lists.html">mailing list</link>
and when to use
<link href="http://nagoya.apache.org/bugzilla/">Bugzilla</link>
(the Apache Bug Database).
</p>
<p>
Research your topic thoroughly before beginning to discuss a new
development issue. Search and browse through the email archives - your
issue may have been discussed before. Prepare your post clearly and
concisely.
</p>
<p>
Most issues will be discovered, resolved, and then patched quickly
via the <code>cocoon-dev</code> mailing list. Larger issues, and ones that
are not yet fully understood or are hard to solve, are destined for
Bugzilla.
</p>
<p>
Experienced developers use Bugzilla directly, as they are very sure
when they have found a bug and when not. However, less experienced users
should first discuss it on the user or developer mailing list (as
appropriate). Impatient people always enter everything into Bugzilla
without caring if it is a bug of Cocoon or their own
installation/configuration mistake - please do not do this.
</p>
<p>
As a rule-of-thumb, discuss an issue on the <code>cocoon-dev</code>
mailing list first to work out any details.
After it is confirmed to be worthwhile, and you are clear about it,
then submit the bug description via Bugzilla.
</p>
<p>
When you are sure about your proposed patch, then please submit it
via Bugzilla, rather than as email to <code>cocoon-dev</code>.
Be sure to add [PATCH] to the summary line, as this enables the automatic
patch alert system to keep track of it. If you do not follow this procedure,
then unfortunately your patch may be over-looked.
</p>
<p>
When posting discussion topics to the <code>cocoon-dev</code> list,
then please be patient.
Perhaps you do not get any answer on your first reply, so just post
it again until you get one. (But please not every hour - allow a few
days for the list to deal with it.) Do not be impatient - remember that
the whole world is busy, not just you. Bear in mind that other countries
will have holidays at different times to your country and that they are
in different time zones. You might also consider re-writing your initial
posting - perhaps it was not clear enough
and the readers' eyes glazed over.
</p>
</s1>
<anchor id="tips"/>
<s1 title="Contribution Notes and Tips">
<p>
This is a collection of tips for contributing to the project in a manner
that is productive for all parties.
</p>
<ul>
<li>
Every contribution is worthwhile. Even if the ensuing discussion
proves it to be off-beam, then it may jog ideas for other people.
</li>
<li>
Use sensible and concise email subject headings. Search engines, and
humans trying to browse a voluminous list, will respond favourably to a
descriptive title.
</li>
<li>
See <link href="mail-lists.html">Tips</link> for Cocoon mailing lists and
<link href="http://learn.to/edit_messages/">Message Editing and
Quoting Guide (with Examples)</link>.
</li>
<li>Start new threads with new Subject for new topics, rather than
re-using the previous Subject line.
</li>
<li>Keep each topic focussed. If some new topic arises then start a new
discussion. This leaves the original topic to continue un-cluttered.
</li>
<li>Whenever you decide to start a new topic, then start with a fresh
new email message window. Do not use the "Reply to" button,
because threaded mail-readers get confused (they utilise the
<code>In-reply-to</code> header). If so, then your new topic will get
lost in the previous thread and go un-answered.
</li>
<li>
Prepend your email subject line with a marker when that is appropriate,
e.g. <code>[Vote]</code>, <code>[Proposal]</code>,
<code>[RT]</code> (Random Thought which quickly blossom into research
topics :-), <code>[STATUS]</code> (development status of a certain
facility).
</li>
<li>
Please follow up with a final posting when your issue is solved. This
should summarise your problem and its solution. Add [SUMMARY] to the
subject line. This will ease the FAQ generation and searching of the list.
Note that some people tend to ignore questions from those that never
follow up.
</li>
<li>
When making changes to XML documentation, or any XML document for that
matter, use a
<link href="http://www.oasis-open.org/cover/">validating parser</link>
(one that is tried and true is
<link href="http://openjade.sourceforge.net/">OpenSP/onsgmls</link>).
This procedure will detect errors without having to go through the whole
<code>build docs</code> process to find them. Do not expect Cocoon
or the build system to detect the validation errors for you - they can
do it, but that is not their purpose. (Anyway, onsgmls validation error
messages are more informative.)
</li>
<li>
Remember that most people are participating in development on a
volunteer basis and in their "spare time". These enthusiasts will attempt
to respond to issues. It may take a little while to get your answers.
</li>
<li>
Research your topic thoroughly before beginning to discuss a new
development issue. Search and browse through the email archives - your
issue may have been discussed before. Do not just perceive a problem and
then rush out with a question - instead, delve.
</li>
<li>
Try to at least offer a partial solution and not just a problem statement.
</li>
<li>
Take the time to clearly explain your issue and write a concise email
message. Less confusion facilitates fast and complete resolution.
</li>
<li>
Do not bother to send an email reply that simply says "thanks".
When the issue is resolved, that is the finish - end of thread.
Reduce clutter.
</li>
<li>
You would usually do any development work against the HEAD branch of CVS.
</li>
<li>
When sending a patch, you usually do not need to worry about which CVS
branch it should be applied to. The maintainers of the repository will
decide.
</li>
<li>
If an issue starts to get bogged down in list discussion, then it may
be appropriate to go into private off-list discussion with a few interested
other people. Spare the list from the gory details. Report a summary back
to the list to finalise the thread.
</li>
<li>
Become familiar with the mailing lists. As you browse and search, you will
see the way other people do things. Follow the leading examples.
</li>
</ul>
</s1>
</body>
</document>
1.8 +7 -0 cocoon-site/src/documentation/content/xdocs/site.xml
Index: site.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/site.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- site.xml 3 Jul 2003 09:46:27 -0000 1.7
+++ site.xml 3 Jul 2003 14:25:02 -0000 1.8
@@ -23,10 +23,17 @@
<community label="Community" href="community/">
<members label="Members" href="members.html"/>
+ <link label="Contributing" href="contrib.html"/>
<link label="Mail Lists" href="mail-lists.html"/>
<link label="Mail Archives" href="mail-archives.html"/>
</community>
+ <menu label="Links" href="link/">
+ <link label="Cocoon Links" href="index.html"/>
+ <link label="Live Sites" href="livesites.html"/>
+ <link label="Cocoon Hosting" href="hosting.html"/>
+ </menu>
+
<external-refs>
<xml.apache.org href="http://xml.apache.org/">
<forrest href="forrest/">
1.3 +1 -2 cocoon-site/src/documentation/content/xdocs/news/archives.xml
Index: archives.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/news/archives.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- archives.xml 16 Jun 2003 07:54:11 -0000 1.2
+++ archives.xml 3 Jul 2003 14:25:03 -0000 1.3
@@ -1,6 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
-"document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
<document>
<header>
<title>Older News</title>
1.5 +1 -2 cocoon-site/src/documentation/content/xdocs/news/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/cocoon-site/src/documentation/content/xdocs/news/index.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.xml 2 Jul 2003 10:55:34 -0000 1.4
+++ index.xml 3 Jul 2003 14:25:03 -0000 1.5
@@ -1,6 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
-"document-v12.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "document-v12.dtd">
<document>
<header>
<title>News</title>
Re: cvs commit: cocoon-site/src/documentation/content/xdocs/news
archives.xml index.xml
Posted by Vadim Gritsenko <va...@verizon.net>.
Joerg Heinicke wrote:
>> cziegeler 2003/07/03 07:25:03
>>
>> Added: src/documentation/content/xdocs/link livesites.xml
>
>
>> Log:
>> Moved common docs to top level
>
>
> A few days ago I divided the livesites list into three parts: 1.x,
> 2.0, 2.1 and committed them to their corresponding CVS module. The
> first reason was to lower the maintenance effort, the second the
> length of the list.
>
> Now we only have one page on top level. Shall I revert the segmentation?
I would prefer separate pages -- so, for example, Lenya also can have
their own "powered by" page.
Vadim
Re: cvs commit: cocoon-site/src/documentation/content/xdocs/news
archives.xml index.xml
Posted by Joerg Heinicke <jo...@gmx.de>.
Done. Maybe there is a better navigation possible?
Joerg
Carsten Ziegeler wrote:
> Joerg Heinicke wrote:
>
>>A few days ago I divided the livesites list into three parts: 1.x, 2.0,
>>2.1 and committed them to their corresponding CVS module. The first
>>reason was to lower the maintenance effort, the second the length of the
>>list.
>>
>>Now we only have one page on top level. Shall I revert the segmentation?
>>
>
> Ups, haven't noticed that. Sorry, I think a segmentation is not bad, but
> I think we should have this segmentation on the top-level rather than
> in the different "version cvs modules". Which means, put the segmentation
> into the cocoon-site module.
>
> Carsten
RE: cvs commit: cocoon-site/src/documentation/content/xdocs/news archives.xml index.xml
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Joerg Heinicke wrote:
>
> A few days ago I divided the livesites list into three parts: 1.x, 2.0,
> 2.1 and committed them to their corresponding CVS module. The first
> reason was to lower the maintenance effort, the second the length of the
> list.
>
> Now we only have one page on top level. Shall I revert the segmentation?
>
Ups, haven't noticed that. Sorry, I think a segmentation is not bad, but
I think we should have this segmentation on the top-level rather than
in the different "version cvs modules". Which means, put the segmentation
into the cocoon-site module.
Carsten
Re: cvs commit: cocoon-site/src/documentation/content/xdocs/news
archives.xml index.xml
Posted by Joerg Heinicke <jo...@gmx.de>.
> cziegeler 2003/07/03 07:25:03
>
> Added: src/documentation/content/xdocs/link livesites.xml
> Log:
> Moved common docs to top level
A few days ago I divided the livesites list into three parts: 1.x, 2.0,
2.1 and committed them to their corresponding CVS module. The first
reason was to lower the maintenance effort, the second the length of the
list.
Now we only have one page on top level. Shall I revert the segmentation?
Joerg