husted 01/02/20 04:25:04
Modified: src/doc installation.xml
Added: src/doc installation-ip.xml
Log:
Add iPlanet instructions.
Submitted by Stanley Santiago.
Revision Changes Path
1.17 +12 -15 jakarta-struts/src/doc/installation.xml
Index: installation.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/src/doc/installation.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- installation.xml 2001/02/19 22:06:38 1.16
+++ installation.xml 2001/02/20 12:25:00 1.17
@@ -217,38 +217,35 @@
to include the <code>struts.jar</code> file (copied earlier) on the
CLASSPATH that is submitted to the compiler.</li>
</ul>
-</section>
-
-<section name="Installing Struts with your servlet container" href="Containers">
-
+</section> <section name="Installing Struts with your servlet container"
href="Containers">
<p>For most containers, you need only to: </p>
-
<ul>
<li>Copy the WAR files in your Struts <code>/webapp</code> directory to your
containers <code>webapps</code> directory. </li>
<li>In some cases, you may need to restart your container if it is running.</li>
</ul>
-
<h3>Status of various containers</h3>
-
<ul>
+ <li>iPlanet Application Server - Service Pack 2 is recommended. See notes
regarding
+ Example Application.</li>
<li>Tomcat 3.1 and prior - Not recommended. Use Tomcat 3.2.1 or later.</li>
<li>Tomcat 3.2.1+ "standalone" - No additional steps required.</li>
<li>Resin 2.1+ "standalone" - No additional steps required.</li>
<li>WebLogic 6.0+ - No additional steps required.</li>
</ul>
-
<ul>
- <li>Bluestone Universal Business Server - <a
href="installation-ubs.html">Additional steps required.</a></li>
+ <li>Bluestone Universal Business Server - <a
href="installation-ubs.html">Additional
+ steps required.</a></li>
+ <li>iPlanet Web Server - <a href="installation-ip.html">Additional steps
required.</a></li>
<li>JRUN - <a href="installation-jrun.html">Additional steps required.</a></li>
- <li>Orion Application Server - <a href="installation-oas.html">Additional steps
required.</a></li>
+ <li>Orion Application Server - <a href="installation-oas.html">Additional steps
+ required.</a></li>
<li>Silverstream - - <a href="installation-sas.html">Additional steps
required.</a></li>
- <li>Tomcat 3.2.1 with Apache - <a href="installation-tc.html">Additional steps
required.</a></li>
- <li>Weblogic 5.1 (sp8) - <a href="installation-wls.html">Additional steps
required.</a></li>
+ <li>Tomcat 3.2.1 with Apache - <a href="installation-tc.html">Additional steps
+ required.</a></li>
+ <li>Weblogic - <a href="installation-wls.html">Additional steps required.</a></li>
<li>WebSphere - <a href="installation-was.html">Additional steps
required.</a></li>
</ul>
-
-
-</section>
+</section>
</body>
</document>
1.1 jakarta-struts/src/doc/installation-ip.xml
Index: installation-ip.xml
===================================================================
<?xml version="1.0"?>
<document url="./installation-ip.xml">
<properties>
<author>Stanley Santiago</author>
<title>The Struts Framework Project - Installation - iPlanet</title>
</properties>
<body>
<section name="Installing Struts with your servlet container" href="Containers">
<h3><a name="ipws42">iPlanet Application Server 6.0</a></h3>
<p>Service Pack 2 is recommended.</p>
<p>NOTE: At present, the Struts example application still uses a non-Serializable
servlet context attribute, and will not run in an environment that requires them,
like iPlanet Application Server.</p>
<h3><a name="ipws42">iPlanet Web Server 4.2</a></h3>
<p>Here are the issues I ran into while moving my struts based application from
Tomcat (supports WebApps and WAR) to iWS 4.1 (does <b>NOT</b> support Webapps
and WAR). </p>
<p>Webapps and WAR will be supported in iWS 5.0, as mentioned in iWS5.0 roadmap.</p>
<h4>Classpath issues.</h4>
<p>This s pretty straightforward. Since there is no notion of
<code>WEB-INF/lib</code> and
<code>WEB-INF/classes</code> the classpath has to be explicitly set in
<code>$SERVER_ROOT/config/jvm12.conf</code>.</p>
<h4>Context relative paths</h4>
<p>All URLs should be visible from the document root. In my case I just created
a symbolic link from <code>$DOCROOT/myapp</code> to <code>webapps/myapp</code>.</p>
<h4>Extension mapping</h4>
<p>The config file <code>$SERVER_ROOT/config/rules.properties</code> has a similar
mechanism
as in web.xml.</p>
<p>I have this in my <code>rules.properties</code> which forwards all urls ending
with "do"
to the servlet whose logical name is action.</p>
<pre>####
@.*[.]do$=action
####</pre>
<hr/>
<ul>
<li>Author: Stanley Santiago</li>
</ul>
<hr/>
<p>Back to <a href="installation.html#Containers">Installation</a></p></section>
</body>
</document>
