Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 64649 invoked by uid 500); 10 Jun 2002 06:55:42 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 64637 invoked from network); 10 Jun 2002 06:55:42 -0000 From: "John Morrison" To: Subject: RE: ClassLoader issues Date: Mon, 10 Jun 2002 07:55:53 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <1023689437.842.17.camel@inspiron> Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: David Haraburda [mailto:david-cocoon@haraburda.com] > > 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. It also runs straight from a java command line. See CLI. I'm +1 as long as there's always the possibility of running it in a backward compatible way. J. --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org