Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Subject: Re: ClassLoader issues
From: David Haraburda <david-cocoon@haraburda.com>
To: cocoon-dev@xml.apache.org
In-Reply-To: <013401c20ffd$be345b40$00350a3e@PC103>
References: <1023648618.845.6.camel@inspiron>
	<013401c20ffd$be345b40$00350a3e@PC103>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 10 Jun 2002 01:10:34 -0500
Message-Id: <1023689437.842.17.camel@inspiron>
Mime-Version: 1.0

Hi,

On Sun, 2002-06-09 at 16:28, Nicola Ken Barozzi wrote:
> The real reason: Cocoon is not a Servlet.
> Cocoon conceptually lives in the same space of Tomcat, not on top of it.

I certainly agree that conceptually Cocoon is much more than a simple
servlet -- it is a large and complex system.  However in actuality it
runs as a web application, so I think it is only appropriate that it
acts in compliance with the necessary specifications.

> 
> Cocoon is generally a servlet out of need, since it eases deployment on
> existing systems.
> 

I can understand with a large project like Cocoon, many things will have
to be done that a normal web application wouldn't do -- the main issue I
am trying to raise here is that I feel it is unnecessary for Cocoon to
ever override the ContextClassLoader -- and I appreciate any and all
feedback on this.

> I'm +1 for having this behaviour being toggeled effectively by the param, so
> I will commit your patch if there are no -1s.
> 

Thanks for the vote and for your time, it is appreciated.

David


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org