Here is an installation how-to for deploying Cocoon with JBoss. (Plus a
small typo-fix ;))
Index: xdocs/installing.xml
===================================================================
RCS file: /home/cvspublic/xml-cocoon2/xdocs/installing.xml,v
retrieving revision 1.5
diff -u -r1.5 installing.xml
--- xdocs/installing.xml 2001/05/23 12:32:22 1.5
+++ xdocs/installing.xml 2001/06/03 09:18:29
@@ -152,7 +152,7 @@
</li>
<li>
- <strong>Copy cocoon/lib/xerces-XXX.jar file to cocoon\lib</strong>
+ <strong>Copy cocoon/lib/xerces-XXX.jar file to tomcat\lib</strong>
Cocoon will now be able to see and use the correct XML libraries.
</li>
@@ -364,6 +364,42 @@
</li>
</ol>
</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
+ 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>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>
+[...]
+# 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"
+[...]
+</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>
</s1>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
