[
https://issues.apache.org/jira/browse/SLING-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328768#comment-14328768
]
Marius Petria edited comment on SLING-4312 at 2/20/15 12:52 PM:
----------------------------------------------------------------
Committed patch in revision 1661081.
EDIT: I reverted the changes in revision 1661109 because the build on java 1.6
was failing. The fail seems to be cause by an incompatibility between
org.apache.sling.commons.testing.2.0.16 and org.osgi.core.4.3.0
{code}
1.6/trunk/bundles/extensions/serviceusermapper/src/test/java/org/apache/sling/serviceusermapping/impl/ServiceUserMapperImplTest.java:[56,62]
findEntries(java.lang.String,java.lang.String,boolean) in
org.apache.sling.commons.testing.osgi.MockBundle cannot implement
findEntries(java.lang.String,java.lang.String,boolean) in
org.osgi.framework.Bundle; attempting to use incompatible return type
found : java.util.Enumeration<?>
required: java.util.Enumeration<java.net.URL>
{code}
was (Author: mpetria):
Committed patch in revision 1661081.
> 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)
