RE: [BUG] CachingPointProcessingPipeline is Configurable and Parameterizable

[Carsten Ziegeler <cz...@s-und-n.de>]

What's the status here, do we want to change it?

Carsten

> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Wednesday, October 29, 2003 12:39 PM
> To: dev@cocoon.apache.org
> Subject: Re: [BUG] CachingPointProcessingPipeline is Configurable and
> Parameterizable
> 
> 
> Carsten Ziegeler wrote:
> 
> >>-----Original Message-----
> >>From: Michael Melhem [mailto:michaelm@managesoft.com]
> >>Sent: Tuesday, October 28, 2003 2:59 PM
> >>To: dev@cocoon.apache.org
> >>Subject: Re: [BUG] CachingPointProcessingPipeline is Configurable and
> >>Parameterizable
> >>
> >>
> >>On Mon, Oct 27, 2003 at 09:37:34AM +0100, Carsten Ziegeler wrote:
> >>    
> >>
> >>>The CachingPointProcessingPipeline is Configurable and Parameterizable
> >>>which is afaik not allowed. I think, this was checked in an earlier
> >>>version of ECM but seems to be not checkec anymore.
> >>>
> >>>As the base class of the processing pipeline is Parameterizable and
> >>>all other pipeline implementations use this interface, it seems
> >>>that Parameterizable is the way to go.
> >>>
> >>>What do you think?
> >>>      
> >>>
> >>OK lets stick with parameterizable then. :) I could make that 
> >>change. Is this a
> >>problem in both the 2.1 and 2.2 branches ?
> >>
> >>    
> >>
> >Yepp, both are "infected" :)
> >
> >I'm +1 for the changes, but they are incompatible, so we should add
> >somewhere (where users find it) some notes about it.
> >  
> >
> 
> status.xml, in <changes/> section?
> 
> Vadim
> 
>