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
I put commons-beanutils.jar into the WEB-INF/lib directory, and I still
get what's copied below from the webpage.
Is my installation possessed or something?
Todd
---
HTTP Status 500 -
type Exception report
message
description The server encountered an
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
Sorry, I just got back from a lengthy vacation (I miss Bali already!).
Answers below:
From: Aidan Mark Humphreys [mailto:[EMAIL PROTECTED]
Just beginning to work with Mav - and struggling slightly.
Taking this as my example,
view name=success path=raw.jsp
transform path=hot.jsp/
From: [EMAIL PROTECTED]
I had a look in the mailing list archives on the discussions
of support for pluggable ControllerFactory-implementations.
I'm wondering what the status on this is. Will Maverick, at
some point, support user defined ControllerFactories? It
would seem natural, given
From: Aidan Mark Humphreys [mailto:[EMAIL PROTECTED]
Another 2 simple questions (in case anyone feels like answering
:).
No problem :-)
This snippet is taken from the domify friend book example.
views
view id=loginRequired path=loginRequired.jsp
