[
https://issues.apache.org/jira/browse/FELIX-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322320#comment-16322320
]
Neil Bartlett commented on FELIX-5770:
--------------------------------------
Fixed in r1820887
> Improve usability and extensibility of SCR commands
> ---------------------------------------------------
>
> Key: FELIX-5770
> URL: https://issues.apache.org/jira/browse/FELIX-5770
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Affects Versions: scr-2.0.14
> Reporter: Neil Bartlett
>
> The scr:list and scr:info commands are hard to use and not as extensible as
> they could be.
> In terms of usability, the output of scr:list is particularly hard to follow,
> with two interleaved tables at different indent levels, i.e.:
> {noformat}
> g! scr:list
> BundleId Component Name Default State
> Component Id State PIDs (Factory PID)
> [ 1] com.effectiveosgi.rt.aws.impl.S3ObjectConverter enabled
> [ 0] [active ]
> [ 1] com.effectiveosgi.rt.aws.s3 enabled
> {noformat}
> It is not very clear what the numbers 0 and 1 represent in each case!
> Also the commands format their output internally, which does not allow the
> formatting to be reused. If the commands simply return DTO objects to the
> Gogo shell and then implement a Converter service to format them, then the
> formatting can be reused by other commands.
> Also the state "SATISFIED" is very confusing when a component throws an
> exception in its activator. This is partly a problem with the OSGi spec
> pre-R7.
> The release of OSGi R7 gives us an opportunity to overhaul these commands and
> improve the formatting. For a proposed reimplementation see
> https://github.com/apache/felix/pull/130
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)