vgritsenko 01/07/22 12:57:22
Modified: xdocs Tag: cocoon_20_branch installing.xml
Log:
Fixed typo, some updates
Revision Changes Path
No revision
No revision
1.6.2.9 +21 -14 xml-cocoon2/xdocs/installing.xml
Index: installing.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/installing.xml,v
retrieving revision 1.6.2.8
retrieving revision 1.6.2.9
diff -u -r1.6.2.8 -r1.6.2.9
--- installing.xml 2001/07/19 13:46:58 1.6.2.8
+++ installing.xml 2001/07/22 19:57:22 1.6.2.9
@@ -161,7 +161,7 @@
</p>
<p>
A library/package is available to the build process when it is located
- in the './lib' directory.
+ in the <code>./lib</code> directory.
</p>
<p>
The following table contains a list of the optional components,
@@ -198,7 +198,10 @@
<td><link href="http://xml.apache.org/fop/index.html";>FOP</link></td>
<td>Yes</td>
</tr>
-</table>
+ </table>
+ <p><strong>Note:</strong> If you added a library/package, you
+ need to rebuild @docname@ as described in 'Create the @docname@ WAR package'.
+ </p>
</s2>
</s1>
@@ -245,7 +248,7 @@
</li>
<li>
- <strong>Copy cocoon/build/cocoon.war into tomcat/webapps</strong>
+ <strong>Copy cocoon/build/cocoon/cocoon.war into tomcat/webapps</strong>
</li>
<li>
@@ -306,7 +309,7 @@
</li>
<li>
- <strong>Copy cocoon/build/cocoon.war into tomcat/webapps</strong>
+ <strong>Copy cocoon/build/cocoon/cocoon.war into tomcat/webapps</strong>
</li>
<li>
@@ -447,38 +450,42 @@
<note>As both JBoss and @docname@ ship with a Hypersonic database installed,
these two conflict and you won't be able to use @docname@ 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">
+ <s2 title="Installing on Resin 2.0.x">
<p>
- This section describes the deployment of the @docname@ sample WAR with
Resin 2.0.0.
+ This section describes the deployment of the @docname@ sample WAR with
Resin 2.0.x.
It assumes that you built @docname@ as described above. All steps have been
tested
- with a fresh Resin 2.0.0 installation (the package is available from
+ with a fresh Resin 2.0.0 and 2.0.1 installations (the package is available
from
<link href="http://www.caucho.com/download/";>Resin's download page</link>)
</p>
<p>After unpacking the Resin package you get the following directory
structure</p>
<source>
[path]...
-[path]/resin-2.0.0/lib
-[path]/resin-2.0.0/webapps
+[path]/resin-2.0.x/lib
+[path]/resin-2.0.x/webapps
[path]...</source>
<p>In order to get @docname@ running you have to install Xerces as default XML
parser for Resin.</p>
<ul>
- <li>Stop the server if it is running.</li><li>Remove the following files
from the <code>resin-2.0.0/lib</code> directory
+ <li>Stop the server if it is running.</li><li>Remove the following files
from the <code>resin-2.0.x/lib</code> directory:
<ul>
<li>jaxp.jar</li>
<li>dom.jar</li>
<li>sax.jar</li>
</ul>
</li>
- <li>Copy the <code>xerces-XXX.jar</code> JAR file from
<code>xml-cocoon2/lib</code> to <code>resin-2.0.0/lib</code> directory
+ <li>Copy the <code>xerces-XXX.jar</code> JAR file from
<code>xml-cocoon2/lib</code> to <code>resin-2.0.x/lib</code> directory
</li>
- <li>Copy the <code>cocoon.war</code> WAR file to
<code>resin-2.0.0/webapps</code> directory
+ <li>Copy the <code>xml-cocoon2/build/cocoon/cocoon.war</code> WAR file to
<code>resin-2.0.x/webapps</code> directory
</li>
- </ul>
- <ul>
<li>Start Resin as usual</li>
<li>Open the @docname@ welcome page (http://localhost:8080/cocoon/)</li>
<li>Congratulations! (hopefully) you should see the @docname@ welcome
page.</li>
</ul>
+ <p><strong>Note:</strong> If you want to place @docname@ webapp in a
+ directory different than <code>resin-2.0.x/webapps</code>, you need
+ to edit <code>resin-2.0.x/conf/resin.conf</code> file and add a line
+ somewhere in <code><![CDATA[<host>]]></code> tag:
+ <source><![CDATA[<web-app id='/cocoon'
app-dir='/path/to/webapp/cocoon.war'/>]]></source>
+ </p>
</s2>
</s1>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
