You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by st...@locus.apache.org on 2000/03/20 22:51:12 UTC
cvs commit: xml-cocoon/xdocs/images add.jpg cocoon2.gif fix.jpg remove.jpg update.jpg
stefano 00/03/20 13:51:12
Added: xdocs Tag: xml-cocoon2 docs-book.xml faq.xml index.xml
installing.xml license.xml site-book.xml
xdocs/dtd Tag: xml-cocoon2 changes-v10.dtd characters.ent
document-v10.dtd faq-v10.dtd javadoc-v04draft.dtd
specification-v10.dtd todo-v10.dtd
xdocs/images Tag: xml-cocoon2 add.jpg cocoon2.gif fix.jpg
remove.jpg update.jpg
Log:
creating cocoon2-alpha1 distribution
Revision Changes Path
No revision
No revision
1.4.2.1 +0 -17 xml-cocoon/xdocs/docs-book.xml
Index: docs-book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/docs-book.xml,v
retrieving revision 1.4
retrieving revision 1.4.2.1
diff -u -r1.4 -r1.4.2.1
--- docs-book.xml 2000/02/23 00:42:51 1.4
+++ docs-book.xml 2000/03/20 21:51:09 1.4.2.1
@@ -6,23 +6,6 @@
<page id="license" label="License" source="license.xml"/>
<page id="install" label="Install" source="installing.xml"/>
<separator/>
- <page id="technologies" label="Technologies" source="technologies.xml"/>
- <page id="infrastracture" label="Infrastructure" source="infrastructure.xml"/>
- <page id="guide" label="User Guide" source="guide.xml"/>
- <page id="dynamic" label="Dynamic Content" source="dynamic.xml"/>
-<separator/>
- <page id="xsp" label="XSP Processor" source="xspprocessor.xml"/>
- <page id="dcp" label="DCP Processor" source="dcpprocessor.xml"/>
- <page id="sql" label="SQL Processor" source="sqlprocessor.xml"/>
- <page id="ldap" label="LDAP Processor" source="ldapprocessor.xml"/>
-<separator/>
- <spec id="wd-xsp" label="XSP WD" source="WD-xsp.xml"/>
-<separator/>
- <external label="Javadocs" href="./api/index.html"/>
-<separator/>
- <page id="cocoon2" label="Cocoon 2" source="cocoon2.xml"/>
- <page id="javadoc" label="Javadoc XML" source="javadoc.xml"/>
-<separator/>
<faqs id="faqs" label="FAQ" source="faq.xml"/>
<changes id="changes" label="Changes" source="changes.xml"/>
<todo id="todo" label="Todo" source="todo.xml"/>
1.6.2.1 +2 -375 xml-cocoon/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/faq.xml,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- faq.xml 2000/03/17 16:44:24 1.6
+++ faq.xml 2000/03/20 21:51:09 1.6.2.1
@@ -5,381 +5,8 @@
<faqs title="Frequently Asked Questions">
<faq>
- <question>I get the exception <em>java.lang.NoClassDefFoundError: sun/tools/javac/Main</em></question>
- <answer>
- <p>
- Look at the question below.
- </p>
- </answer>
-</faq>
-
-<faq>
- <question>I can't get XSP to work. What might be wrong?</question>
- <answer>
- <p>
- The XSP processor requires a single configuration that might cause problems:
- the repository location for compiled server pages.
- </p>
-
-<source>processor.xsp.repository = ./repository</source>
-
- <p>
- If the process that runs the servlet engine doesn't have both reading
- and writing persmissions on that directory, the XSP processor won't work, so
- make sure you locate that directory to a safe place.
- </p>
-
- <note><strong>Warning:</strong>
- Since this directory may contain security sensible information, make sure
- you deny access (even read-only) to untrusted users.
- </note>
-
- <p>
- Another common problem is the system complaining about missing classes such as:
- </p>
-
- <source>java.lang.NoClassDefFoundError: sun/tools/javac/Main</source>
-
- <p>
- If this happens, make sure you have installed the <code>tools.jar</code>
- package you find in <code>[jdk_home]/lib/tools.jar</code>.
- </p>
- </answer>
-</faq>
-
-<faq>
- <question>I get the exception <em>Can't create store repository: //./repository.
-Make sure it's there or you have writing permissions.</em> How do I fix this?
- </question>
- <answer>
- <p>Create a directory where the servlet engine process is owner and has 600 access mask.
- Then change the following configuration to match the absolute path:</p>
-
- <source>processor.xsp.repository = /absolute/path/to/repository</source>
-
- <p>then restart your servlet engine.</p>
-
- <note>The repository may contain sensible information you don't want untrusted
- users to gain access to. This is why you should restrict both write and read
- by all but the servlet engine process.</note>
- </answer>
-</faq>
-
-<faq>
- <question>what are the other jar files shipped with Cocoon for? do I need to include them into my classpath?</question>
- <answer>
- <p>They are for building Cocoon and creating its docs from XML but they are not used by Cocoon at runtime so, if you
- don't plan to modify and recompile Cocoon or its documentation, you can safely ignore them.</p>
- </answer>
-</faq>
-
-<faq>
- <question>can I place <em>cocoon.jar</em> in my servlet context or servlet zone instead of my classpath?</question>
- <answer>
- <p>Due to a problem in most custom classloader implementations (for example, both JServ and Tomcat suffer from this problem) local resources
- cannot be loaded if they are located in custom repositories and packaged inside zip/jar files.</p>
- <p>A workaround is to expand the <em>cocoon.jar</em> file and like that directory as your servlet context repository
- or place the required resources in your classpath or wait for this problem to be fixed.</p>
- </answer>
-</faq>
-
-<faq>
- <question>I get the exception <em>java.lang.AbstractMethodError: org/apache/jserv/JServContext.getContext</em>. What's wrong?</question>
- <answer>
- <p>You are probably using JServ with the wrong version of the Servlet Library. JServ supports Servlet API 2.0
- and is not forward compatible with the newer version shipped with Cocoon. Cocoon is Servlet API 2.2 compatible and
- requires the servlet_2.2.jar package to compile correctly, but works is back compatible with old servlet engines.</p>
- <p>To fix the problem you must set the Servlet API 2.0 version in your classpath instead of the one shipped with
- cocoon. Read the JServ installation instructions for more info on this.</p>
- </answer>
-</faq>
-
-<faq>
- <question>Why the LDAP processor doesn't work?</question>
- <answer>
- <p>Make sure you have the <link href="http://java.sun.com/products/jndi/index.html">Sun JNDI API</link>
- package installed in your classpath.</p>
- </answer>
-</faq>
-
-<faq>
- <question>Why DCP doesn't work with EcmaScript anymore? Where do I find the class <code>FESI/jslib/JSObject</code>?</question>
- <answer>
- <p>Since Cocoon now ships with all the required packages and Fesi is a
- very big package, we decided to make Ecmascript support for DCP optional.</p>
- <p>So, you should turn on the language interpretation in the cocoon
- configurations and place the <link href="http://home.worldcom.ch/jmlugrin/fesi/download.html">
- FESI</link> package in your classpath.</p>
- <note>the DCP processor should be considered deprecated and we do not guarantee
- that will be supported in future versions. We highly suggest you to
- transfor all of your DCP pages into XSP pages.</note>
- </answer>
-</faq>
-
-<faq>
- <question>How come Apache is not redirecting requests to Cocoon?</question>
- <answer>
- <p>There is a bug in mod_jserv that makes it dependent on its configuration
- position. If you use <em>ApJServHandler</em> you should change this to more
- standard <em>Action and AddHandler</em>. If you installed an old version
- of Cocoon, read again the installation instructions to find a solutions for
- this problem. (thanks to Dan Egnor for finding and solving the problem).</p>
- </answer>
-</faq>
-
-<faq>
- <question>How do I pipe my servlet output into Cocoon?</question>
- <answer>
- <p>Simple answer: <em>you don't!!!</em> read <connect href="dynamic.xml">the page
- about dynamic content</connect> to find out equivalent ways to do what you need.</p>
- <p>Complex answer: the Servlet API <em>was not</em> 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
- into the request of another. Currently (version 2.2) the Servlet API spec
- doesn't allow a servlet to post-process the output of another servlet, so,
- since Cocoon is a servlet, there is no portable way for it to call
- your servlet and to process its output.</p>
- <p>The Cocoon Project is in close contact with the Servlet API Expert Group at
- Sun (being Stefano Mazzocchi a member of that board) and will propose
- post-processing hooks for inclusion in the next Servlet API specifications.
- Since this is work in progress, please, don't fill up the mail list with
- questions about this: Cocoon will reflect the API changes as soon as they
- are publicly available.</p>
- </answer>
-</faq>
-
-<faq>
- <question>Where do I get more information on XSL and XML?</question>
- <answer>
- <p>
- The web community is very exited about XML and XSL and many sources of
- information are coming up even if these languages are fairly new. Here is a list of
- locations you might be interested in to continue to gather resources on this
- state-of-the-art technology</p>
- <ul>
- <li><link href="http://www.xml.org">http://www.xml.org</link> - A very nice site for XML
- information.</li>
- <li><link href="http://www.w3.org/xml/">http://www.w3.org/xml/</link> - The XML
- official home page at W3C</li>
- <li><link href="http://www.w3.org/style/xsl">http://www.w3.org/style/xsl</link> - The XSL official
- home page W3C</li>
- <li><link href="http://www.software.ibm.com/xml/education/tutorial-prog/abstract.html">http://www.software.ibm.com/xml/education/tutorial-prog/abstract.html</link>
- - XML Tutorial from IBM</li>
- <li><link href="http://www.webtechniques.com/features/1999/01/walsh/walsh.shtml">http://www.webtechniques.com/features/1999/01/walsh/walsh.shtml</link>
- - XSL Tutorial</li>
- <li><link href="http://www.oasis-open.org/cover/xml.html">http://www.oasis-open.org/cover/xml.html</link>
- - XML Resource Listing</li>
- <li><link href="http://www.oasis-open.org/cover/xsl.html">http://www.oasis-open.org/cover/xsl.html</link>
- - XSL Resource Listing</li>
- <li><link href="http://www.xmlsoftware.com">http://www.xmlsoftware.com</link> -
- XML software listing</li>
- <li><link href="http://www.xmlinfo.com">http://www.xmlinfo.com</link> - XML
- information updates on W3C status and others</li>
- <li><link href="http://www.xslinfo.com">http://www.xslinfo.com</link> - XSL
- information, updates, example stylesheets</li>
- <li><link href="http://www.schema.net">http://www.schema.net</link> - Repository
- of standard DTDs</li>
- </ul>
-</answer>
-</faq>
-
-<faq>
- <question>Are there document translations to other languages?</question>
- <answer>
- <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><link href="http://www.epita.net">French Translation</link></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>
- </answer>
-</faq>
-
-<faq>
- <question>Why do I keep getting FileNotFoundException under Tomcat 3.0?</question>
- <answer><p>See question below</p></answer>
-</faq>
-
-<faq>
- <question>How come Cocoon doesn't work on Tomcat 3.0?</question>
- <answer>
- <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><![CDATA[ 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>
- </answer>
-</faq>
-
-<faq>
- <question>Are external entities still broken?</question>
- <answer>
- <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>
- </answer>
-</faq>
-
-<faq>
- <question>I see that Cocon 1.x has starting to incorporate features planned for
- Cocoon 2.x, why?</question>
- <answer>
- <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>
- </answer>
-</faq>
-
-<faq>
- <question>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?
- </question>
- <answer>
- <p>The PI <code><?xml:stylesheet type="text/xsl" href=""?></code>
- is the old method of associating a stylesheet with an XML document. Unfortunately, this
- technology is rapidly changing and your books should warn you that the topic they are
- 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
- <link href="http://www.w3.org/TR/xml-stylesheet">http://www.w3.org/TR/xml-stylesheet</link> and
- clearly indicates that <code><?xml-stylesheet ...?></code> is the proper way.</p>
- </answer>
-</faq>
-
-<faq>
- <question>
- 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?
- </question>
- <answer>
- <p>You are right, PI reaction breaks the context separation and it's, at the
- very end, the wrong approach. To follow a complete "model, view,
- controller" design pattern, one should be able to associate a different
- 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 <connect href="cocoon2.xml">Cocoon2
- outline</connect>) 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
- behavior of their documents in one place without having to modify every
- single reactive PI in each source file.</p>
- <p>So, you've been warned: the PIs will go away, current functionality will
- remain but the processing management will be abstracted one layer up.</p>
-</answer>
-</faq>
-
-<faq>
-<question>What is WAP and how do I browse WML?</question>
-<answer>
- <p>WAP stands for Wireless Application Protocol and WML stands for Wireless
- Markup Language. For more information about these two, please refer to the
- <link href="http://www.wapforum.org">WAP Forum</link>. For a client able
- to browse WML 1.1, Cocoon has been tested with the
- <link href="http://www.nokia.com">Nokia WAP Toolkit</link> which
- emulates a Nokia WAP cell phone on your desktop.</p>
-</answer>
-</faq>
-
-<faq>
-<question>What is VoxML and how do I browse VML?</question>
-<answer>
- <p>VoxML is a voice markup language, designed to allow direct integration
- between voice recognition/synthesis software and web technologies.
- The Cocoon VML samples have been tested with the
- <link href="http://www.voxml.org">Motorola VoxML SDK 1.1</link>(for windows)
- which is freely available.</p>
-</answer>
-</faq>
-
-<faq>
-<question>Why is my Internet Explorer not showing PDF or VRML samples?</question>
-<answer>
- <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>
-</answer>
-</faq>
-
-<faq>
-<question>When I compile Cocoon on my system, I get all a bunch of errors. What's wrong?</question>
-<answer>
- <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
- use.</p>
- <p>Note that if you tried to compile Cocoon.java alone, many classes are not compiled
- because there is no hardcoded reference to them. Cocoon uses dynamic loading based on its
- property file to get the modules it needs when started. For this reason, the compiler is
- not able to tell which class will be use and its dependency checks are never complete. The
- 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>
-</answer>
-</faq>
-
-<faq>
- <question>Why the name "Cocoon"?</question>
- <answer>
- <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 <em>afficionado</em>, I found out
- that Ron Howard's movie <em>Cocoon</em> 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
- for the thing, meaning to be a way to bring new life to old ideas as well as to create <em>cocoons</em>
- for such new ideas to become beautiful butterflies. :-)</p>
-</answer>
+ <question></question>
+ <answer></answer>
</faq>
</faqs>
1.3.2.1 +2 -2 xml-cocoon/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/index.xml,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -u -r1.3 -r1.3.2.1
--- index.xml 2000/03/19 00:58:06 1.3
+++ index.xml 2000/03/20 21:51:09 1.3.2.1
@@ -15,7 +15,7 @@
<s1 title="What is it?">
<p>
- <img src="images/cocoon.jpg" alt="Cocoon"/> Cocoon is a 100% pure
+ <img src="images/cocoon2.gif" alt="Cocoon"/> Cocoon is a 100% pure
Java publishing framework that relies on new W3C
technologies (such as DOM, XML, and XSL) to provide web content.
</p>
@@ -177,7 +177,7 @@
</p>
<p>
- Thank you very much. <img src="images/cocoon-small.jpg" alt="Powered by Cocoon"/>
+ Thank you very much.
</p>
</s1>
</body>
1.8.2.1 +1 -316 xml-cocoon/xdocs/installing.xml
Index: installing.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/installing.xml,v
retrieving revision 1.8
retrieving revision 1.8.2.1
diff -u -r1.8 -r1.8.2.1
--- installing.xml 2000/03/16 13:41:16 1.8
+++ installing.xml 2000/03/20 21:51:09 1.8.2.1
@@ -7,8 +7,6 @@
<title>Installing Cocoon</title>
<authors>
<person name="Stefano Mazzocchi" email="stefano@apache.org"/>
- <person name="Brett McLaughlin" email="bmclaugh@algx.net"/>
- <person name="Russell Castagnaro" email="russell@synctank.com"/>
</authors>
</header>
@@ -22,7 +20,7 @@
<ul>
<li><strong>Java Virtual Machine</strong>
- A Java 1.1 or greater compatible virtual machine must be present for both
+ A Java 1.2 or greater compatible virtual machine must be present for both
command line and servlet type usage of Cocoon. Note that all servlet engines
require a JVM to run so if you are already using servlets you already have
one installed.
@@ -167,319 +165,6 @@
report or a request for help on the mail lists. Thank you.
</note>
</s2>
-
- <s2 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
- classpath provided to Java classes that use constructs such as
- <code>Class.forName().newInstance()</code>. The second classpath is
- associated with a specific context, and is somewhat analagous to the
- servlet zones used in Apache JServ (see section above).
- </p>
-
- <p>
- Because the Cocoon framework utilizes <code>Class.forName()</code> and other
- dynamic instance handling techniques, the Cocoon classes need to have its
- classpath aware of the component classes used within the framework. To do
- this, take all the required components (see above) and put them in your
- <em><Tomcat-Root>/lib</em> directory. This is the standard location
- for Tomcat core libraries. To ensure that Tomcat will use these, you need
- to edit the Tomcat startup file.
- </p>
-
- <p>
- On Windows, this is <em><Tomcat-Root>/tomcat.bat</em> and on
- Unix, this is <em><Tomcat-Root>/tomcat.sh</em>. In this
- file you must add all the component jar files to Tomcat's classpath.
- </p>
-
- <note>
- from this version of Cocoon the <code>cocoon.jar</code>
- package should be added to the servlet engine classpath as any other
- required package (as shown above).
- </note>
-
- <p>
- 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 <em>web.xml</em> file in your context's
- <em>WEB-INF</em> directory (look in <code>src/WEB-INF/</code> to find a
- template <em>web.xml</em>). This file specifies servlet mappings
- and initial arguments to servlets and looks like this:
- </p>
-
-<source><![CDATA[
-<servlet>
- <servlet-name>org.apache.cocoon.Cocoon</servlet-name>
- <servlet-class>org.apache.cocoon.Cocoon</servlet-class>
- <init-param>
- <param-name>properties</param-name>
- <param-value>
- [path-to-cocoon.properties]/cocoon.properties
- </param-value>
- </init-param>
-</servlet>
-
-<servlet-mapping>
- <servlet-name>org.apache.cocoon.Cocoon</servlet-name>
- <url-pattern>*.xml</url-pattern>
-</servlet-mapping>
-]]></source>
-
- <p>
- Make sure you replaced the path to the Cocoon.properties file with the
- actual location of that file on your system.
- 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
- brief indications and comments on the different configurations, but you
- don't need to care about that at this point.
- </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>
- 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 <em>jakarta.apache.org</em>.
- We apologize for this, but it's not something we can control or work
- around.
- </note>
- </s2>
-
- <s2 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>
- package to your <code>weblogic.class.path</code> variable either
- using the <em>t3config</em> utility or use the <code>-Dweblogic.class.path</code>
- argument with the java runtime that invokes the system.
- </p>
- <p>
- Once you've done that, you should register Cocoon by adding these lines
- to your configuration files:
- </p>
-<source>weblogic.httpd.register.*.xml=\org.apache.cocoon.Cocoon
-weblogic.httpd.initArgs.*.xml=\properties=[path-to-cocoon]/bin/cocoon.properties</source>
- <p>
- making sure that you replaced <em>[path-to-cocoon]</em> 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>
- 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>
-
- </s2>
-
- <s2 title="Installing Cocoon on other platforms">
- <p>Yet to be written! <em>Volunteers welcome!</em></p>
- </s2>
-
- </s1>
-
- <s1 title="Working Systems">
- <p>
- Cocoon has been reported to be working on these systems:
- </p>
-
- <table>
- <tr>
- <th>Operating System</th>
- <th>Web Server</th>
- <th>Servlet Engine</th>
- <th>JVM</th>
- </tr>
- <tr>
- <td>RedHat Linux 6.0</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.0</td>
- <td>IBM JDK 1.1.8</td>
- </tr>
- <tr>
- <td>RedHat Linux 6.0</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.1b3</td>
- <td>IBM JDK 1.1.8</td>
- </tr>
- <tr>
- <td>RedHat Linux 6.0</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.0</td>
- <td>Blackdown JDK 1.2pre2</td>
- </tr>
- <tr>
- <td>RedHat Linux 6.1</td>
- <td>Apache 1.3.9</td>
- <td>JRun 2.3.3</td>
- <td>IBM JRE 1.1.8</td>
- </tr>
- <tr>
- <td>RedHat Linux 6.1 (i686)</td>
- <td>Apache 1.3.11</td>
- <td>Apache JServ 1.1</td>
- <td>Sun JDK 1.2.2</td>
- </tr>
- <tr>
- <td>RedHat Linux 6.1 (i686)</td>
- <td>Apache 1.3.11 + mod_ssl 2.5.0</td>
- <td>Apache JServ 1.1</td>
- <td>IBM JDK 1.1.8</td>
- </tr>
- <tr>
- <td>Windows 98</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.0</td>
- <td>Sun JDK 1.2.2</td>
- </tr>
- <tr>
- <td>Windows 98</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.0</td>
- <td>IBM JDK 1.1.7</td>
- </tr>
- <tr>
- <td>Windows 98</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.1b3</td>
- <td>Sun JDK 1.2.2</td>
- </tr>
- <tr>
- <td>Windows 98</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.1b3</td>
- <td>IBM JDK 1.1.7</td>
- </tr>
- <tr>
- <td>Windows 98</td>
- <td>MS Personal Web Server</td>
- <td>ServletExec 2.2</td>
- <td>Sun JDK 1.2.1</td>
- </tr>
- <tr>
- <td>Windows NT 4.0</td>
- <td>IIS 4.0</td>
- <td>ServletExec 2.2</td>
- <td>Sun JDK 1.2.1</td>
- </tr>
- <tr>
- <td>Windows NT 4.0</td>
- <td>IIS 4.0</td>
- <td>JRun 2.3.3</td>
- <td>Sun JDK 1.2.1</td>
- </tr>
- <tr>
- <td>Windows NT 4.0</td>
- <td>Apache 1.3.9</td>
- <td>JRun 2.3.3</td>
- <td>Sun JDK 1.2.2</td>
- </tr>
- <tr>
- <td>Windows NT 4.0</td>
- <td colspan="2">Apache Jakarta Tomcat 3.1 Milestone 1</td>
- <td>Sun JDK 1.2.2</td>
- </tr>
- <tr>
- <td>MacOS 8.6</td>
- <td>WebSTAR 4.0</td>
- <td>JRun 2.3</td>
- <td>MrJ 2.1.4</td>
- </tr>
- <tr>
- <td>MacOS 8.6</td>
- <td>WebSTAR 4.0</td>
- <td>ServletExec 2.1</td>
- <td>Mrj 2.1.4</td>
- </tr>
- <tr>
- <td>MacOS 8.6</td>
- <td>Quid Pro Quo 2.1.3</td>
- <td>ServletExec 2.2</td>
- <td>Mrj 2.1.4</td>
- </tr>
- <tr>
- <td>SunOS Netria 5.6</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.1b3</td>
- <td>Sun JDK 1.1.7</td>
- </tr>
- <tr>
- <td>FreeBSD 3.4</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.0</td>
- <td>Blackdown JDK 1.1.8</td>
- </tr>
- <tr>
- <td>SCO OpenServer 5</td>
- <td colspan="2">WebLogic 4.5.1</td>
- <td>SCO JDK 1.1.7A</td>
- </tr>
- <tr>
- <td>MacOS 8.5+</td>
- <td colspan="2">Resin 1.1b</td>
- <td>MRJ 2.2</td>
- </tr>
- <tr>
- <td>FreeBSD 3.4-STABLE with linux_base-6.1 for linux-emulation</td>
- <td colspan="2">Jetty Java HTTP Server v2.3.3</td>
- <td>Blackdown jdk-1.2.2-RC4-linux-i386-glibc</td>
- </tr>
- <tr>
- <td>SuSE 6.3 Linux</td>
- <td>Apache 1.3.9</td>
- <td>Apache JServ 1.1</td>
- <td>Sun JDK 1.2.2</td>
- </tr>
- <tr>
- <td>OS/2 Warp 4 FP 12</td>
- <td colspan="2">Gefion Software LiteWebServer</td>
- <td>IBM JDK 1.1.8</td>
- </tr>
- <tr>
- <td>SGI IRIX 6.5.7</td>
- <td>Apache 1.3.12</td>
- <td>Apache JServ 1.1</td>
- <td>Sun JDK 1.2.1 (SGI)</td>
- </tr>
- </table>
-
- <note>
- Due to a bug in <link href="http://www.blackdown.org">Blackdown
- JDK 1.2pre2</link> 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.
- </note>
- <p>
- Please, submit your feedback on the cocoon user mail list (nowhere else!) if
- you were able to install Cocoon on a different combination not listed above.
- Thanks.
- </p>
</s1>
</body>
</document>
1.2.2.1 +0 -0 xml-cocoon/xdocs/license.xml
Index: license.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/license.xml,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
1.4.2.1 +0 -15 xml-cocoon/xdocs/site-book.xml
Index: site-book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/site-book.xml,v
retrieving revision 1.4
retrieving revision 1.4.2.1
diff -u -r1.4 -r1.4.2.1
--- site-book.xml 2000/02/24 23:31:24 1.4
+++ site-book.xml 2000/03/20 21:51:09 1.4.2.1
@@ -10,21 +10,6 @@
<page id="license" label="License" source="license.xml"/>
<page id="install" label="Install" source="installing.xml"/>
<separator/>
- <page id="infrastracture" label="Infrastructure" source="infrastructure.xml"/>
- <page id="technologies" label="Technologies" source="technologies.xml"/>
- <page id="guide" label="User Guide" source="guide.xml"/>
- <page id="dynamic" label="Dynamic Content" source="dynamic.xml"/>
-<separator/>
- <page id="xsp" label="XSP Processor" source="xspprocessor.xml"/>
- <page id="dcp" label="DCP Processor" source="dcpprocessor.xml"/>
- <page id="sql" label="SQL Processor" source="sqlprocessor.xml"/>
- <page id="ldap" label="LDAP Processor" source="ldapprocessor.xml"/>
-<separator/>
- <spec id="wd-xsp" label="XSP WD" source="WD-xsp.xml"/>
-<separator/>
- <page id="cocoon2" label="Cocoon 2" source="cocoon2.xml"/>
- <page id="javadoc" label="Javadoc XML" source="javadoc.xml"/>
-<separator/>
<faqs id="faqs" label="FAQ" source="faq.xml"/>
<changes id="changes" label="Changes" source="changes.xml"/>
<todo id="todo" label="Todo" source="todo.xml"/>
No revision
No revision
1.3.2.1 +0 -0 xml-cocoon/xdocs/dtd/changes-v10.dtd
Index: changes-v10.dtd
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/dtd/changes-v10.dtd,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -u -r1.3 -r1.3.2.1
1.1.2.1 +0 -0 xml-cocoon/xdocs/dtd/characters.ent
Index: characters.ent
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/dtd/characters.ent,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
1.1.2.1 +0 -0 xml-cocoon/xdocs/dtd/document-v10.dtd
Index: document-v10.dtd
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/dtd/document-v10.dtd,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
1.2.2.1 +0 -0 xml-cocoon/xdocs/dtd/faq-v10.dtd
Index: faq-v10.dtd
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/dtd/faq-v10.dtd,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
1.2.2.1 +0 -0 xml-cocoon/xdocs/dtd/javadoc-v04draft.dtd
Index: javadoc-v04draft.dtd
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/dtd/javadoc-v04draft.dtd,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
1.2.2.1 +0 -0 xml-cocoon/xdocs/dtd/specification-v10.dtd
Index: specification-v10.dtd
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/dtd/specification-v10.dtd,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
1.2.2.1 +0 -0 xml-cocoon/xdocs/dtd/todo-v10.dtd
Index: todo-v10.dtd
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/dtd/todo-v10.dtd,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
No revision
No revision
1.1.2.1 +0 -0 xml-cocoon/xdocs/images/add.jpg
<<Binary file>>
1.1.2.1 +0 -0 xml-cocoon/xdocs/images/cocoon2.gif
<<Binary file>>
1.1.2.1 +0 -0 xml-cocoon/xdocs/images/fix.jpg
<<Binary file>>
1.1.2.1 +0 -0 xml-cocoon/xdocs/images/remove.jpg
<<Binary file>>
1.1.2.1 +0 -0 xml-cocoon/xdocs/images/update.jpg
<<Binary file>>