Paul Hammant wrote:
>
> Some apps may want to update their own configuration. I presume as one
>Configuration...
>
> interface SelfConfigurer {
> void configure(Configuration);
> }
>
> interface SelfConfigurable {
> void setSelfConfigurer(SelfConfigurer selfConfigurer);
> }
>
> What thought?
If a Component want's to manage its own configuration (which is not too uncommon),
then they do not need to implement the Configurable interface. That interface
is used to configure child elements.
For example, in Cocoon, the main object does not implement the Configurable interface.
It uses a method called configure() (no arguments) to separate out the main config
code.
Bottom line is that it is up to the Component builder to decide how to handle
self configuration.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
