AFAICS, Tomcat (at least 4.1.18) has its own commons-beanutils.jar in
its server/lib. It could conflict with the one you added to Tomcat
classpath.
The jars in Tomcat's server/lib directory are not visible from
webapps.
However, the jars in common/lib and shared/lib are.
That's it. But
I removed commons-beanutils.jar from the Tomcat classpath (which you
can set in Eclipse using the Preferences pane) and was able to compile.
It also then ran the Log4jInit code someone suggested I create...of
course, only after producing the warnings that code was meant to stop
from
work.
HTH,
yurazlin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Todd O'Bryan
Sent: Tuesday, February 10, 2004 12:20 PM
To: [EMAIL PROTECTED]
Subject: Re: [Mav-user] Eclipse, log4j, etc.
I removed commons-beanutils.jar from the Tomcat classpath (which you
The problem may not be directly with the BeanUtils class, but rather a
class it imports. For all of our installations, we have the following
commons jars in every webapp's WEB-INF/lib directory:
commons-beanutils
commons-collections
commons-lang
commons-logging
Actually, that's a bit of a
Thanks for the help. That didn't fix it. The weekend's over and I'm
back at work, so it will probably be
Friday before I have a chance to look at everything again.
Todd
On Feb 8, 2004, at 1:48 PM, Ed Thompson wrote:
I have the following in my web.xml:
servlet
AFAICS, Tomcat (at least 4.1.18) has its own commons-beanutils.jar in
its server/lib. It could conflict with the one you added to Tomcat
classpath.
The jars in Tomcat's server/lib directory are not visible from webapps.
However, the jars in common/lib and shared/lib are.
I have the following in my web.xml:
servlet
servlet-namelog4j-init/servlet-name
servlet-classorg.ed4becky.mComics.Log4jInit/servlet-class
init-param
param-namelog4j-init-file/param-name
param-valueWEB-INF/log4j.properties/param-value
/init-param
