[
https://issues.apache.org/jira/browse/KARAF-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated KARAF-1077:
---------------------------------------
Description:
The current service:list command shows bundles and the services they offer or
use.
I propose to move that functionality to the bundle:list command or to a new
bundle:services command as the main resource ist the bundle and the service
only shows at the second level. As there are already commands like
bundle:headers the bundle:services variant sounds like a good option for me?
Any opionions here?
For service:list I would like to change the functionality to focus on services
as the first level. Here is my current design:
SYNTAX
service:list [-p] [-u] [servicename] [filter]
ARGUMENTS
fqServiceName fully qualified service name or service name or wildcard like
MySer*
filter ldap filter to query for properties
OPTIONS
-p Show bundles providing this service
-u Show bundles using this service
--prop Showw service properties
Output is the list of matching services. Depending on the options different
levels of details are shown
<objectClass1, objectClass2, ...>
=============
<key1>=<value1>
<key2>="<value2>", ...
Provided by :
-------------
<bundle1>
Used by :
---------
<bundle2> <query used to bind the service>
<bundle3> ...
was:
The current service:list command shows bundles and the services they offer or
use.
I propose to move that functionality to the bundle:list command or to a new
bundle:services command as the main resource ist the bundle and the service
only shows at the second level. As there are already commands like
bundle:headers the bundle:services variant sounds like a good option for me?
Any opionions here?
For service:list I would like to change the functionality to focus on services
as the first level. Here is my current design:
SYNTAX
service:list [-p] [-u] [servicename] [filter]
ARGUMENTS
fqServiceName fully qualified service name or service name or wildcard like
MySer*
filter ldap filter to query for properties
OPTIONS
-p Show bundles providing this service
-u Show bundles using this service
--prop Showw service properties
Output is the list of matching services. Depending on the options different
levels of details are shown
<objectClass1, objectClass2, ...>
=============
Providers
---------
<bundle1> <key1>="<value1>", <key2>="<value2>", ...
<bundle2> ...
Consumers
---------
<bundle1> <query used to bind the service>
<bundle2> ...
> New service:list command focused on services instead of bundles
> ---------------------------------------------------------------
>
> Key: KARAF-1077
> URL: https://issues.apache.org/jira/browse/KARAF-1077
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> The current service:list command shows bundles and the services they offer or
> use.
> I propose to move that functionality to the bundle:list command or to a new
> bundle:services command as the main resource ist the bundle and the service
> only shows at the second level. As there are already commands like
> bundle:headers the bundle:services variant sounds like a good option for me?
> Any opionions here?
> For service:list I would like to change the functionality to focus on
> services as the first level. Here is my current design:
> SYNTAX
> service:list [-p] [-u] [servicename] [filter]
> ARGUMENTS
> fqServiceName fully qualified service name or service name or wildcard like
> MySer*
> filter ldap filter to query for properties
> OPTIONS
> -p Show bundles providing this service
> -u Show bundles using this service
> --prop Showw service properties
> Output is the list of matching services. Depending on the options different
> levels of details are shown
> <objectClass1, objectClass2, ...>
> =============
> <key1>=<value1>
> <key2>="<value2>", ...
> Provided by :
> -------------
> <bundle1>
> Used by :
> ---------
> <bundle2> <query used to bind the service>
> <bundle3> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
