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? -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
