Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <444D0ECF.1090008@apache.org>
Date: Mon, 24 Apr 2006 11:45:51 -0600
From: Jeff Genender <jgenender@apache.org>
Reply-To: jgenender@apache.org
Organization: Apache Geronimo
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: [jira] Created: (GERONIMO-1903) Add Spring to default class
 ignore
 list
References: <14915906.1145900465678.JavaMail.jira@brutus>
In-Reply-To: <14915906.1145900465678.JavaMail.jira@brutus>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

This goes beyond Spring (and Commons Logging).  It affects antlr too
when using Hibernate.  I am sure there are a plethora of other
jar/packages this will affect too.

Should we take a closer look at our classloaders and figure out why we
need to do this?

Jeff

Aaron Mulder (JIRA) wrote:
> Add Spring to default class ignore list
> ---------------------------------------
> 
>          Key: GERONIMO-1903
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1903
>      Project: Geronimo
>         Type: Bug
>     Security: public (Regular issues) 
>   Components: web  
>     Versions: 1.1    
>     Reporter: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
> 
> 
> It's pretty dumb that anyone deploying a Spring app has to manually add classloader excludes to their Geronimo plan.  We should support Spring out of the box.  Which until we improve our CL structure means that we need to add default excludes for Spring itself plus potentially any libraries commonly shared between Spring/Acegi/etc. and Geronimo.
> 
> I guess we need a test app for this.
>