You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/12/10 11:05:00 UTC
[jira] [Updated] (SLING-7297) Add methods to wait for OSGi
components and OSGi services
[ https://issues.apache.org/jira/browse/SLING-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-7297:
-----------------------------------
Description:
Sometimes in an IT you need to wait for a specific OSGi component or service to be available (i.e. active). Just waiting for the bundle is not necessarily enough, as the contained services/components might not yet have been started. Therefore having the following additional two methods would be beneficial:
# {{waitComponentActive(String componentName, long, long}} to wait until the component with given name is active and
# {{waitServiceAvailable(String serviceType, String bundleSymbolicName, long, long)}} to wait until a service of the given type is available. If the bundleSymbolicName is not null it should also check that this service is being registered from the given bundle.
The following ReST calls against the Apache Felix WebConsole can be used to check for that.
{{/system/console/components/<componentName>.json}} returns metadata about a specific component. All services are listed via {{/system/console/services.json}}. This can be used to extract information about a specific service.
See also the related discussion at: https://mail.osgi.org/pipermail/osgi-dev/2017-December/006638.html
was:
Sometimes in an IT you need to wait for a specific OSGi component or service to be available (i.e. active). Just waiting for the bundle is not necessarily enough, as the contained services/components might not yet have been started. Therefore having the following additional two methods would be beneficial:
# {{waitComponentActive(String componentName, long, long}} to wait until the component with given name is active and
# {{waitServiceAvailable(String serviceType, String bundleSymbolicName, long, long)}} to wait until a service of the given type is available. If the bundleSymbolicName is not null it should also check that this service is being registered from the given bundle.
The following ReST calls against the Apache Felix WebConsole can be used to check for that.
{{/system/console/components/<componentName>.json}} returns metadata about a specific component. All services are listed via {{/system/console/services.json}}. This can be used to extract information about a specific service.
> Add methods to wait for OSGi components and OSGi services
> ---------------------------------------------------------
>
> Key: SLING-7297
> URL: https://issues.apache.org/jira/browse/SLING-7297
> Project: Sling
> Issue Type: Improvement
> Components: Apache Sling Testing Clients
> Affects Versions: Apache Sling Testing Clients 1.1.4
> Reporter: Konrad Windszus
>
> Sometimes in an IT you need to wait for a specific OSGi component or service to be available (i.e. active). Just waiting for the bundle is not necessarily enough, as the contained services/components might not yet have been started. Therefore having the following additional two methods would be beneficial:
> # {{waitComponentActive(String componentName, long, long}} to wait until the component with given name is active and
> # {{waitServiceAvailable(String serviceType, String bundleSymbolicName, long, long)}} to wait until a service of the given type is available. If the bundleSymbolicName is not null it should also check that this service is being registered from the given bundle.
> The following ReST calls against the Apache Felix WebConsole can be used to check for that.
> {{/system/console/components/<componentName>.json}} returns metadata about a specific component. All services are listed via {{/system/console/services.json}}. This can be used to extract information about a specific service.
> See also the related discussion at: https://mail.osgi.org/pipermail/osgi-dev/2017-December/006638.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)