I've had a few similar problems with this, almost always caused by 2
different commons-logging jars being on the classpath. However, I have
not had this problem with Jetty... I have commons-logging 1.0.3 and
log4j 1.2.8 running on my classpath (and cayenne-nodeps.jar of course)
and Jetty starts up fine. I am embedding jetty in my application, as
opposed to starting jetty externally, so the difference could be in
the way jetty bootstraps, I suppose..
I haven't spent much time using Tapestry. Does it include its own
commons-logging? That may be where the conflict is coming from.
Cris
On 4/20/05, Erik Hatcher <eri..hatchersolutions.com> wrote:
> Oh, and I'm using cayenne-nodeps.jar now as well. I've added more of
> JAR's that ship with Jetty to my <java> classpath and Jetty now
> launches successfully... still logging is not working exactly right,
> but I'm at least functional now.
>
> Erik
>
This archive was generated by hypermail 2.0.0 : Wed Apr 20 2005 - 14:13:17 EDT