[
https://issues.apache.org/jira/browse/FELIX-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264260#comment-14264260
]
Felix Meschberger commented on FELIX-4704:
------------------------------------------
While I appreciate this patch and the importance of the service.ranking
property, I really think the service.ranking property is not important on a
general level. But maybe it makes sense to expose it explicitly in the list.
Regardless, I still have some issues with the simplistic approach here: First I
don't think we should show the service.ranking in the second column even before
the service types. Maybe the last column is more appropriate.
Second, and more subtle, though, is that the service.ranking property is not
generally used on a global level across all services but amongst services of a
specific type. So I doubt the general usefulness of sorting the global service
table by the service.ranking property.
> Show ranking in web console services plugin
> -------------------------------------------
>
> Key: FELIX-4704
> URL: https://issues.apache.org/jira/browse/FELIX-4704
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Reporter: Alexander Klimetschek
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: webconsole-4.2.6
>
> Attachments: FELIX-4704.patch, screenshot.png
>
>
> The service ranking is an important property of services and one often needs
> to look for all implementations of a given service and sort them by their
> ranking - to list them in the order they are used by some other component.
> Thus adding a new column to the services table that can be sorted like the
> other ones would be really helpful. Filtering down to one service interface
> is already possible since FELIX-4202 (e.g. {{(objectclass=*.MyService}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
