> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Mark Woon
> Sent: Sunday, 10 February, 2002 14:39
> To: Avalon Developers List
> Subject: Re: Parametarizable incompatible with Configurable?
>
>
> Stephen McConnell wrote:
>
> > In the case of Parameterizable and Configurable, both interfaces
> > are basically providing solutions to the same "notion". To
> > have an object that implemented both would be inconsistent - it
> > would be like saying that to understand something, you need to
> > deliver that information in two different and distinct forms.
> > This would conflict with the pipeline notion in Avalon - where
> > the fulfilment of a particular phase raises the objects
> > level of awareness, and readiness for higher things (... its almost
> > a religious experience). Applying both Parameterizable and
> > Configurable on the same object would be conceptually irrational,
> > informational inconsistent, and a touch frustrating for the object
> > in question :-)
>
> Heh. I see.
>
> I brought this up because the "Developing With Apache Avalon"
> document does not match this philosophy: "Usually this interface is
> used in lieu of the Configurable interface, however if both are used,
> the parameterize() method is called after the configure() method."
>
> I'm curious, is this actually enforced by a ComponentManager?
There are a number of classes that enforce component pipline phases.
One example I am familiar with is the Phoenix LifecycleHelper.
http://cvs.apache.org/viewcvs.cgi/jakarta-avalon-phoenix/src/java/org/apache
/avalon/phoenix/components/application/LifecycleHelper.java
This example demopnstrates the OR condition between Configurable
and Parameterizable.
Cheers, Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
