Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: Renaud Bruyeron <bruyeron@fullsix.com>
Subject: Re: isolate the pipeline "component" from rest of cocoon
Date: Fri, 20 Oct 2006 16:33:51 +0200
Lines: 35
Message-ID: <ehamod$skb$1@sea.gmane.org>
References: <eh9ulr$s4u$1@sea.gmane.org> <4538C399.6000206@reverycodes.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.7 (X11/20060922)
In-Reply-To: <4538C399.6000206@reverycodes.com>
Sender: news <news@sea.gmane.org>

Vadim Gritsenko wrote:
> Renaud Bruyeron wrote:
>>
> It is possible to use pipelines directly, it would look something like:
> 
>   ...setup container...

Is that the avalon container, or is it a spring container? Is there an 
example of this somewhere?

> 
>   ProcessingPipeline pipeline = new [Non]CachingProcessingPipeline();
>   pipeline.enableLogging(...);
> 
>   while (...) {
>     pipeline.setup(new Parameters());
> 
>     // Pipeline will get generator from container
>     pipeline.setGenerator("file", ...);
>     pipeline.addTransformer("xslt", ...);
>     pipeline.setSerializer("html", ...);
> 
>     Environment env = new BackgroundEnvironment(...);
>     pipeline.process(env);
>     pipeline.recycle();
>   }

This looks simple enough. The recycle() method is not part of the 
ProcessingPipeline interface, but all its implementations are Recyclable 
(I guess this is avalon speak for "to be used in a pool", and therefore 
I can assume that the implementations are not threadsafe, right?).
Am I correct in assuming that cocoon pools instances of the pipelines 
(one per thread) when in a webapp context ?

  - Renaud