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.
Cheers
Niclas
On Thursday 22 January 2004 11:08, Leo Sutic wrote:
> I therefore propose the addition of the following interface to
> org.apache.avalon.framework.configuration
> public interface MutableConfiguration extends Configuration
> {
> public void setValue( final String value );
> public void setValue( final int value );
> public void setValue( final long value );
> public void setValue( final boolean value );
> public void setValue( final float value );
> public void setAttribute( final String name, final String value );
> public void setAttribute( final String name, final int value );
> public void setAttribute( final String name, final long value );
> public void setAttribute( final String name, final boolean value );
> public void setAttribute( final String name, final float value );
> public String addAttribute( final String name, String value );
> public void addAll( final Configuration other );
> public void addAllChildren( final Configuration other );
> public void removeChild( final Configuration configuration );
> }
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
