[jira] [Comment Edited] (FELIX-6607) Web Console Plugins should have a predictable order in case of label conflicts

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724149#comment-17724149 ] 

Konrad Windszus edited comment on FELIX-6607 at 5/19/23 6:38 AM:
-----------------------------------------------------------------

That makes internal plugins win over external ones having no ranking or ranking of zero. That is IMHO counter-intuitive as usually the web console bundle (and its services) is loaded first (i.e. one would assume a lower service id for internal plugin).


was (Author: kwin):
That makes internal plugins win over external ones having no ranking or ranking of zero. That is IMHO counter-intuitive as usually the web console is loaded first (i.e. one would assume a lower service id for internal plugin).

> Web Console Plugins should have a predictable order in case of label conflicts
> ------------------------------------------------------------------------------
>
>                 Key: FELIX-6607
>                 URL: https://issues.apache.org/jira/browse/FELIX-6607
>             Project: Felix
>          Issue Type: Improvement
>          Components: Web Console
>            Reporter: Konrad Windszus
>            Priority: Major
>
> In case two web console plugins register for the same label it is currently not predictable which is getting used (because the service being started later overwrites earlier ones with the same label). The regular ServiceReference.compareTo(…) semantics should be used to determine which of the conflicting plugins should win.
> Internal plugins which do not rely on OSGi services (and therefore don't have a servicereference) should have the highest priority (i.e. should not be allowed to be overwritten).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)