Iplanet 6.0 Application Server has war support..it is J2EE
certifiedIplanet Web Server will
Include a war deployment tool and support in version 5 due out shortly...
charles Beckham
-Original Message-
From: Paul Hendley - Sun Microsystems [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 16, 2001 4:16 PM
To: [EMAIL PROTECTED]
Subject: Re: Deploying Struts on iPlanet 4.1 - any successes?
Hi Craig,
Some of my coworkers looked at this and came to a similar conclusion as you
mention. (ie no WAR file support in IPlanet) Not sure if things are any
different in version 6.0, but for now this prompted us to use Tomcat instead
of
IPlanet for the time being.
-Paul
Mailing-List: contact [EMAIL PROTECTED]; run by
ezmlm
list-help: mailto:[EMAIL PROTECTED]
list-unsubscribe:
mailto:[EMAIL PROTECTED]
list-post: mailto:[EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
From: "Randall, Craig" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Deploying Struts on iPlanet 4.1 - any successes?
MIME-Version: 1.0
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
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
