geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruce Snyder <>
Subject Re: [jira] Updated: (GERONIMO-518) Deploying Struts app fails on Logging ClassCastException
Date Fri, 30 Sep 2005 06:25:30 GMT
On 9/29/05, Aaron Mulder <> wrote:
> For my part, I've never been arguing that this was a good way to
> construct an application.  I'm simply saying that if we as Geronimo
> developers insist that people change their applications to work in
> Geronimo, then we have a windmill issue.  Even if we all agree that
> putting commons logging in the WEB-INF/lib stinks, the fact is that
> people do it, and do it for the most common web framework out there,
> and those application do not break in other application servers.  In
> my opinion, RTFM is not the correct position for us to take.
> Since we have an obvious workaround available (that is, making the
> list of packages to exclude configurable, and putting commons logging
> in there), why don't we plan to implement it?

I think we do plan to do that, but it's a long term solution.

> An alternative would be to restructure the class loaders so the client
> cannot see any server classes including logging -- where the client
> and server class loader trees are both rooted in a common class loader
> with (more or less) only the spec JARs.  I think this would be a great
> approach, and I believe there was some wider interest in looking at
> it, but it does not seem like a short-term (1.0-era) change.

I think that's one part of the solution regardless. The 2.4 servlet
spec states that this should be the case. I'll even go a step further
and say that Commons Logging should be removed altogether. IMO, we
should be using Log4J or SLF4J instead.

perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"

The Castor Project

Apache Geronimo

View raw message