Although I need this sort of mechanism myself, I am not supportive of this proposal in its current form, and feel a vote is a bit pre-mature, especially since it involves Framework.
-1.
IMHO, I think this should be bundled with nailing down the Reconfigurable() semantics and life cycle as well.
I believe it could use a little more thought. But I also believe the Reconfigurable interface is one of the ill conceived interfaces that were kept from pre Avalon 4 days.
Truthfully, with a combination of a ConfigurationListener type of interface then the component can be notified when the configuration changes externally. This approach is better and potentially more scalable than adding in and reparsing the entire configuration tree again. Also less confusing than receving any partial configuration tree and then trying to determine which configuration element it was that changed.
Then again, performing the configuration like beans would be more natural to a larger group of individuals so there are a dozen directions you can go.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
