Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <1075748481.401e9e8175ff1@localhost>
Date: Mon,  2 Feb 2004 11:01:21 -0800
From: "Craig R. McClanahan" <craigmcc@apache.org>
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: Jakarta Collections 3.0?
References: <20040123222953.28771.qmail@nagoya.betaversion.org>
 <40193262.50705@ptc.com> <4019351F.9000509@apache.org>
 <bvh5mn$4qe$1@sea.gmane.org> <bvjals$cvd$1@sea.gmane.org>
In-Reply-To: <bvjals$cvd$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2

Quoting Costin Manolache <cmanolache@yahoo.com>:

> If I remember correctly ( and if it didn't change ), tomcat needs 
> modeler in a parent classloader. Modeler has an optional dependency on 
> digester, which depends on beanutils and collections. They both depend 
> on logging, and modeler also depends on jmx.
> 
> So unless some classloader trick is used - we have to have collections 
> in the parent loader - which forces the entire tomcat instalation to use 
> the same collection version ( unless reverse loader tricks are used ).
> That implies that if tomcat upgrades to collections3.0 - all webapps 
> that use collections2.0 may stop working.
> 
> Even more interesting - we don't actually have this choice - since if 
> digester changes to the new collections, we're forced to do the same :-)
> 
> 
> What if we use modeler without digester ? Are there other components 
> that depend on digester + collections ? At least for emebed this would 
> be a good solution ( it won't reduce the size too much, but it may 
> reduce the dependency impact it has when it's embeded - since whatever 
> app it is emebeded into will be forced to update collections and all 
> packages that depend on it - or do classloader tricks )
> 

Subscribers to COMMONS-DEV will see that I'm proposing to remove the dependency
on [collections] from both [beanutils] and [digester].  Both dependencies are
very thin, and doing this will avoid penalizing [beanutils]/[digester]
customers for what [collections] did.

> 
> Costin
> 

Craig


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org