You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/12/08 12:00:13 UTC
[jira] [Comment Edited] (SLING-4217) Register OSGi services
corresponding to available adapter factories
[ https://issues.apache.org/jira/browse/SLING-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235373#comment-14235373 ]
Robert Munteanu edited comment on SLING-4217 at 12/8/14 10:59 AM:
------------------------------------------------------------------
I posted the patch for review at https://reviews.apache.org/r/28751/ since I find it much easier to look at diffs this way
was (Author: rombert):
I also posted a review at https://reviews.apache.org/r/28751/ since I find it much easier to look at diffs this way
> Register OSGi services corresponding to available adapter factories
> -------------------------------------------------------------------
>
> Key: SLING-4217
> URL: https://issues.apache.org/jira/browse/SLING-4217
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Adapter 2.1.2
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Adapter 2.1.4
>
>
> As discussed on [dev@:Using adapters on Sling startup|http://markmail.org/message/e4m26rpt3lqe2o2b], we need a more stable way of knowing when an adapter is available. The AdapterManager already publishes OSGi Events, but those are can't be easily mixed with SCR Components.
> [~justinedelson] suggested that we register services for each adapter factory and add them as references to the services which require the adapters to be registered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)