You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hivemind.apache.org by "karthik.nar" <ka...@gmail.com> on 2006/10/30 15:06:34 UTC
set-configuration versus set-object
Hello,
Pardon me if this is a really silly question. I'm a hivemind newbie.
I get the sense that these two are equivalent
<set-configuration property="contributions"
configuration-id="ServiceEncoders"/>
<set-object property="contributions" value="configuration:ServiceEncoders"/>
Am I correct?
If I'm correct, when would I choose to use one syntax over the other?
Thanks, Karthik.
--
View this message in context: http://www.nabble.com/set-configuration-versus-set-object-tf2539538.html#a7074926
Sent from the Hivemind - User mailing list archive at Nabble.com.
Re: set-configuration versus set-object
Posted by Knut Wannheden <kn...@gmail.com>.
Karthik,
Yes, the two are equivalent. You have the choice due to historical
reasons. First there was only <set-configuration>, then when
<set-object> was added the other was not removed to remain backwards
compatible.
HTH,
--knut
On 10/30/06, karthik.nar <ka...@gmail.com> wrote:
>
> Hello,
>
> Pardon me if this is a really silly question. I'm a hivemind newbie.
>
> I get the sense that these two are equivalent
>
> <set-configuration property="contributions"
> configuration-id="ServiceEncoders"/>
> <set-object property="contributions" value="configuration:ServiceEncoders"/>
>
> Am I correct?
>
> If I'm correct, when would I choose to use one syntax over the other?
>
> Thanks, Karthik.
>
> --
> View this message in context: http://www.nabble.com/set-configuration-versus-set-object-tf2539538.html#a7074926
> Sent from the Hivemind - User mailing list archive at Nabble.com.
>
>