blob: 02b01af46529c0a97dec073875475bff07c5a774 [file] [log] [blame]
<?xml version="1.0"?>
<document url="./installation-ip.xml">
<author>Stanley Santiago</author>
<title>The Struts Framework Project - Installation - iPlanet</title>
<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
<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/</code> has a similar mechanism
as in web.xml.</p>
<p>I have this in my <code></code> which forwards all urls ending with &quot;do&quot;
to the servlet whose logical name is action.</p>
<li>Author: Stanley Santiago</li>
<p>Back to <a href="installation.html#Containers">Installation</a></p></section>