were u actually able to get Struts 1.1 b2 to work with iplanet 6?
I was able to fix the logging problem by making a small change in the
ActionServlet, however I was having problems with the parsing of
struts-config.xml by the Digester class.
Since then I've given up on using Struts 1.1 b2 and instead i'm using Struts
1.0.2.

-----Original Message-----
From: Ortega, Carlos [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 3:04 PM
To: Struts Users Mailing List
Subject: RE: Struts w/ iPlanet6


All,

I recieved this bit of advice from Dasa Paddock (see next message), if you
are having problems getting Struts to work properly with iPlanet 6, the
advice in his message helped tremendously.

Also, If you're using Struts with PoolMan's connection pool, be sure to
place both the the commons-logging.jar and log4j.jar in the JVM classpath
with commons appearing first. There seems to be a conflict between the two
JAR files.

Regards,
Carlos Ortega
------------------------------------------------------------------------

Carlos,

I'm also using iPlanet 6.  I'm using the Web Server SP 2, not the App
Server.

The only way I got it to work was to put the commons-logging.jar into the
JVM classpath.  And I had to put the one from Struts 1.1 Beta 1, not Beta 2.
This is a known problem and happens on some other servlet engines as well.
The Struts guys say that it's a bug in iPlanet's (and the others) servlet
engine.  Also make sure that you have the ActionServlet configured to
automatically start in the web.xml if you're going to a JSP page before
anything else.

I've also found that in Beta 2, it won't find the Resource.properties file
unless it is also in the classpath.  I just put it in the iPlanet config
directory.

This is a pain and I sure home that it's fixed in the upcoming Sun One
Server 7!

--Dasa Paddock
Application Developer

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to