Hello,
here's a patch for the JBoss documentation I contributed some weeks
ago.
Sven....
Index: xdocs/installing.xml
===================================================================
RCS file: /home/cvspublic/xml-cocoon2/xdocs/installing.xml,v
retrieving revision 1.8
diff -u -r1.8 installing.xml
--- xdocs/installing.xml 2001/06/12 12:59:46 1.8
+++ xdocs/installing.xml 2001/06/12 18:30:25
@@ -321,40 +321,62 @@
</s2>
<s2 title="Installing on JBoss 2.2.2 with Tomcat 3.2.2">
<p>This section describes the deployment of the Cocoon 2 sample WAR with
- the JBoss 2.2.2/Tomcat-3.2.2 package. It assumes that you built Cocoon 2 as
described above. All steps have been tested with a fresh JBoss 2.2.2 installation (the
package is available from <link href="http://sourceforge.net/projects/jboss/";>JBoss'
project page</link>)</p>
- <p>When unpacking the JBoss/Tomcat package you get the following directory
+ the JBoss 2.2.2/Tomcat-3.2.2 package. It assumes that you built Cocoon 2 as
+described above. All steps have been tested with a fresh JBoss 2.2.2 installation on
+Linux and Windows ME(sic).</p>
+ <note>The JBoss/Tomcat bundle is available from the <link
+href="http://sourceforge.net/projects/jboss/";>JBoss project page</link></note>
+ <p>The JBoss/Tomcat package has the following directory
structure</p>
<source>
[path]/JBoss-2.2.2_Tomcat-3.2.2/jboss
[path]/JBoss-2.2.2_Tomcat-3.2.2/tomcat
</source>
- <p>Subsequently, <code>jboss</code> denotes the
<code>JBoss-2.2.2_Tomcat-3.2.2/jboss</code> directory and <code>cocoon</code> is the
base directory of your Cocoon 2 distribution or CVS checkout.</p>
+ <p>Subsequently, </p>
+ <ul><li><code>jboss</code> denotes the
+<code>JBoss-2.2.2_Tomcat-3.2.2/jboss</code> directory</li>
+ <li><code>tomcat</code> is short for
+<code>JBoss-2.2.2_Tomcat-3.2.2/tomcat</code></li><li>and <code>cocoon</code> is the
+base directory of your Cocoon 2 distribution or CVS checkout.</li></ul>
<p>In order to get Cocoon 2 running you have to install Xerces as default XML
parser for JBoss.</p>
- <ul><li>Stop the server if it is running.</li><li>Remove the following files
from the <code>jboss/lib</code>
directory<ul><li>jaxp.jar</li><li>parser.jar</li><li>xml.jar</li><li>crimson.jar</li></ul></li>
- <li>Copy the <code>xerces-XXX.jar</code> and <code>xalan-XXX.jar</code> JAR
files from <code>cocoon/lib</code> to <code>jboss/lib</code></li>
- <li>Change the <code>jboss/bin/run.sh</code></li>
-</ul>
- <source>
+ <ul>
+ <li>Stop the server if it is running.</li>
+ <li>Remove the following files from the <code>jboss/lib</code> directory
+ <ul>
+ <li>crimson.jar</li>
+ <li>jaxp.jar</li>
+ <li>xml.jar</li>
+ </ul>
+ </li>
+ <li>Remove the following files from the <code>tomcat/lib</code>
+ directory
+ <ul>
+ <li>jaxp.jar</li>
+ <li>parser.jar</li>
+ </ul>
+ </li>
+ <li>Copy <code>xerces-XXX.jar</code> from <code>cocoon/lib</code> to
+<code>jboss/lib</code></li>
+ <li>Change <code>jboss/bin/run.sh</code></li>
+ </ul>
+ <source>
[...]
# Add the XML parser jars and set the JAXP factory names
# Crimson parser JAXP setup(default)
-# Change it to Xerces for C2
-JBOSS_CLASSPATH=$JBOSS_CLASSPATH:../lib/xerces-XXX.jar:../lib/xalan-XXX.jar
-# Comment out the following two lines as Xerces' JAXP implementation sets
-# these appropriately.
-#JAXP=-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
-#JAXP="$JAXP
-Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.jaxp.SAXParserFactoryImpl"
+<strong># Change it to Xerces for C2</strong>
+JBOSS_CLASSPATH=$JBOSS_CLASSPATH:<strong>../lib/xerces-XXX.jar</strong>
+<strong># Remove the following two lines</strong>
+<em>JAXP=-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
+JAXP="$JAXP
+-Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.jaxp.SAXParserFactoryImpl"</em>
[...]
-</source>
-<note>Windows users have to change <code>run.bat</code> accordingly.</note>
- <ul><li>Start JBoss with <code>run_with_tomcat.sh</code> or
<code>run_with_tomcat.bat</code></li>
- <li>Copy <code>cocoon/build/cocoon/cocoon.war</code> to
<code>jboss/deploy</code></li>
- <li>Open the Cocoon welcome page (http://localhost:8080/cocoon/)</li>
- <li>
- Congratulations! (hopefully) you should see the Cocoon welcome page.
- </li></ul>
- <note>As both JBoss and Cocoon 2 ship with a Hypersonic database installed,
these both conflict and you won't be able to view the Cocoon database (SQL) samples.
Then again, you probably use JBoss for EJB persistence anyway, so this shouldn't
bother you to much ;-)</note>
- </s2>
+ </source>
+ <note>Windows users have to change <code>run.bat</code> accordingly.
+ </note>
+ <ul>
+ <li>Start JBoss with <code>run_with_tomcat.sh</code> or
+<code>run_with_tomcat.bat</code></li>
+ <li>Copy <code>cocoon/build/cocoon/cocoon.war</code> to
+<code>jboss/deploy</code></li>
+ <li>Check the server log to make sure that <code>J2EE application:
+[...]/cocoon.war is deployed.</code></li>
+ <li>Open the Cocoon welcome page (http://localhost:8080/cocoon/)</li>
+ <li>
+ Congratulations! (hopefully) you should see the Cocoon welcome page.
+ </li>
+ </ul>
+ <note>As both JBoss and Cocoon 2 ship with a Hypersonic database installed,
+these two conflict and you won't be able to use Cocoon's database (SQL) samples. Then
+again, you probably use JBoss for EJB persistence anyway, so this shouldn't bother
+you too much ;-)
+ </note>
+ </s2>
<s2 title="Installing on Resin 2.0.0">
<p>
This section describes the deployment of the Cocoon 2 sample WAR with Resin
2.0.0.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
