then You can treat the configuration as Map , there would have conflict with the same key duplicated in any module.
But If you don't specify key-attribute, then the configuration point is treated as List, list don't conflict at all, It only add the same thing twice.
Felix Sun
On 5/6/06,
Nicholas Clare <[EMAIL PROTECTED]> wrote:
On 5/6/06, Tat leung < [EMAIL PROTECTED]> wrote:Hi All,
I have a module (A) which defines a configuration point. I have two
other modules (B and C) which both define contributions to the same
configuration point defined in A. Will the contributions in B and C be
in conflict with each other?
Thanks,
Tat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]Hi Tat,
As far as I know, it depends on how many contributions you've allowed the configuration point to have (in the occurs attribute of the configuration-point). If it's just one, then there will be an error, but if you've allowed more (either 1..n or unbounded), then it should be fine.
I may be wrong, since I'm pretty new to HiveMind, but I hope this helps,
Nick
