RE: Deploying Struts on iPlanet 4.1 - any successes?

[Lou . Farho]

Title: Deploying Struts on iPlanet 4.1 - any successes?

As you have already gathered iWS does not support war files.  As far as iPlanet iAS 6.0, I have been trying to run Struts on it.  So far I have not been able to, due to an apparent failure of iPlanet to implement section 5.4 of the Servlet 2.2 spec. correctly.

PS.  You should distinguish between the iPlanet Web Server (iWS 4.1) and iPlanet Application Server (iAS6.0) in the future to prevent any confusion.

 

Good Luck

-----Original Message-----
From: Randall, Craig [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 16, 2001 5:11 PM
To: [EMAIL PROTECTED]
Subject: Deploying Struts on iPlanet 4.1 - any successes?

I've searched for "iPlanet" on the Struts mail list archive (), and based on the few (17) hits, I wanted to verify explicitly with this group whether or not anyone else has successfully deployed a web application on this server. Has anyone?

Although 4.1 is touted to support JSP 1.1/Servlet 2.2, I see no support for WAR files! I'm trying to map configuration files on my Solaris 2.7 installation of iPlanet 4.1, and believe that following to be true:

        - /usr/iplanet4.1/https-admserv/config/contexts.properties
                - this is where "/<app-built-on-struts>" goes (i.e. the context name
                  declaration/configuration)
                        - classpath specification (since there is no implicit spec based
                          on WEB-INF...)
                        - session configuration, encoding configuration, etc.
        - /usr/iplanet4.1/https-admserv/config/servlets.properties
                - this is where the equivalent of <servlet> elements in web.xml
                  goes, where an association is made to the proper "context name"
                  in contexts.properties
        - /usr/iplanet4.1/https-admserv/config/rules.properties
                - this is where the equivalent of <servlet-mapping> elements in web.xml
                  goes, where an association is made to the proper "context name"
                  in contexts.properties
        - /usr/iplanet4.1/https-admserv/config/mime.types
                - this is where the equivalent of <mime-mapping> elements in web.xml
                  goes

Can anyone else confirm my theory?

If iPlanet 4.1 is not viable, is version 6.0 any better?

TIA.

-Craig