[ https://issues.apache.org/jira/browse/SLING-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292403#comment-16292403 ]
Konrad Windszus commented on SLING-7297: ---------------------------------------- [~andrei.dulvac] Can you have a look at the attached PR? > OSGiConsoleClient: 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.12 > Reporter: Konrad Windszus > Assignee: 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: > # {{waitComponentRegistered(String componentName, long, long}} to wait until > the component with given name is active and > # {{waitServiceRegistered(String Type, 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. > Unfortunately there is not yet the possibility to extract services by type > (FELIX-5761). > 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)