Leo Simons wrote:
>>But out-of-date.
>>The lifecycle descriptions are missing a few things:
>>
>> b) Serviceable is missing
>>
>
>where does it go?
>
Serviceable should appear wherever Composable appears. Basically
Serviceable is a replacement for Composable - Serviceable takes a
ServiceManager as (as distinct from Composable/ComponentManager).
ServiceManager is independent of the Component marker interface
enabling broader application and support for existing "non-Avalon"
components (because ServiceManager exposes java.lang.Object as distinct
from Component).
>> a) configurable OR paramerterizable (choice
>>
>
>when did this happen? Why?
>
More than a year or two ago.
From the Javadoc:
public interface Configurable
This interface should be implemented by classes that need to
be configured with custom parameters before initialization.
The contract surrounding a Configurable is that the instantiating
entity must call the configure method before it is valid. The
configure method must be called after the constructor, and before
any other method.
Note that this interface is incompatible with Parameterizable.
The above semantics are enforced in both Merlin and Phoenix - I don't
know what the status is with ECM (because I don;t use ECM).
>> b) composable OR serviceable (choice)
>>
>
>you probably ment a), b), c) :D
>
I did :-)
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
