[
https://issues.apache.org/jira/browse/SLING-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328926#comment-14328926
]
Marius Petria commented on SLING-4312:
--------------------------------------
[~cziegeler], the ServiceUserMapperImplTest uses MockBundle only to produce a
bundle with a custom symbolic name. That can easily be done with mockito
directly without relying on MockBundle [1]. Relying on mockito makes everything
green even on Java 6.
However I have one question: is it ok to introduce the dependency on
osgi.core.4.3.0?
[1]
https://github.com/mpetria/sling/commit/f28a0eca06003f5d5d309ed4797ee01fa557cfa2
> Register an osgi service for each available service user
> ---------------------------------------------------------
>
> Key: SLING-4312
> URL: https://issues.apache.org/jira/browse/SLING-4312
> Project: Sling
> Issue Type: Improvement
> Components: Service User Mapper
> Reporter: Marius Petria
> Attachments: SLING-4312.diff
>
>
> In order to only activate osgi components when a service user mapping is
> available it would be useful to have an osgi service registered for a service
> user. A component can reference the registered service name and only start
> when that becomes available.
> {code}
> @Reference(target="(name=serviceName)")
> ServiceUserExists userExists;
> {code}
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
