On Thursday 15 February 2007 15:11, David Leangen wrote:
> Ok, sounds reasonable. So you want to have hard-coded, pre-
> compilation values, is that it?
Well, we are not abandoning the runtime aspects at all. Everything can still
be changed in runtime, for instance Assume that you have three
menus, "m1", "m2" and "m3" defined as ContentAggregators. Now, if you create
a MenuItem (which is a ContentSource) as "Logout" and originally has the
Destination array being { "m1.Logout", "m3.Logout" }, then the Logout
menuitem will be wired to "m1" and "m3". Configuration Admin allows for
arrays, so by changing the "Destination" array to
{ "m1.Logout", "m2.Logout" } you will remove the menu item from "m3" and add
it to "m2".
> Then an array as you suggested would work. Or, if you want to be even
> more explicit, you could maybe use a hashmap so that the user can
> also add a small description or something. I guess a full-blown class
> would be overkill in this case.
Are you suggesting that the "wire" contains additional description, or is it
enough if we add localized description support for the ContentSource
instances?
Cheers
Niclas
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
