Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (nike.apache.org: domain of scherler@gmail.com designates
 74.125.82.179 as permitted sender)
Message-ID: <1325587524.10084.5.camel@mcKenny>
Subject: Re: [C3] cocoon-sample / cocoon-archetype-block and rcl
From: Thorsten Scherler <scherler@gmail.com>
To: dev@cocoon.apache.org
Date: Tue, 03 Jan 2012 11:45:24 +0100
In-Reply-To: <4F02CD4F.3070709@apache.org>
References: <4F02CD4F.3070709@apache.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Mime-Version: 1.0

On Tue, 2012-01-03 at 10:41 +0100, Francesco Chicchiriccò wrote:
> Hi devs,
> cocoon-sample and cocoon-archetype-block do use cocoon-maven-plugin to
> prepare and deploy a block to a local jetty, featuring some class
> reloading feature.
> 
> It could be an idea to remove cocoon-maven-plugin and profit from
> class reloading features of Tomcat 7 [1] (for instance) with support
> of Cargo for managing and configuring Tomcat instance.
> 
> We may, of course, continue (actually, start again) support for
> cocoon-maven-plugin. but I have more a feeling that we could better
> concentrate on C3 development, instead.
> 
> WDYT?
> 

Actually I think Igor has made a cut on the rcl using spring rcl
instead. I would rather not force to use tomcat and bound us there.
However if we can extract Igors work in this area I would be +1 to drop
our own stuff in favor for spring.

salu2

> Regards.
> 
> [1]
> http://tomcat.apache.org/tomcat-7.0-doc/config/loader.html#Common_Attributes
> [2] http://cargo.codehaus.org/Tomcat+7.x 
> -- 
> Francesco Chicchiriccò
> 
> Apache Cocoon Committer and PMC Member
> http://people.apache.org/~ilgrosso/

-- 
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/