On Tue, 2002-10-01 at 09:54, Peter Donald wrote:
> On Tue, 1 Oct 2002 23:42, Jason van Zyl wrote:
> > Just wondering what the standard way of modifying a configuration at
> > runtime is?
>
> Generally the component can not modify it's own configuration. The container
> *may* modify it and pass it back to the component using Reconfigurable (but
> if it does the semantics are not clearly defined).
>
> > Or if this isn't generally practiced how do you add new elements to
> > DefaultConfiguration or CascadingConfiguration. The Javadocs for
> > setValue(String s) aren't exactly clear as to what a value is? Is this
> > an XML fragment?
>
> No - just the content of an element. To add a new Node at runtime I believe
> the name of the methods are addChild()/removeChild(). The one thing that you
> can't do is to remove a attribute (though you can set it to null). I think
> this is a bug we just never got around to fixing ;)
Ok, I have something like this:
<rendererConfiguration>
<properties>
<property name="x" value="y"/>
<!-- Add more properties here -->
</properties>
</rendererConfiguration>
I want to add more <property/> elements. Know off hand how to do that?
>
>
> --
> Cheers,
>
> Peter Donald
> He strains to hear a whisper who refuses to hear a shout.
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
