[
https://issues.apache.org/jira/browse/SLING-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326085#comment-14326085
]
Marius Petria commented on SLING-4312:
--------------------------------------
Hi [~cziegeler]
I implemented the bundle filter such that the mapping is visible only for those
that can use it [1]. ([~bosschaert] pointed me in the right direction)
The amendments are treated because I hooked myself just before/after the
activeBindings are updated.
I have two questions related to my current impl.
1. The ServiceUserMapping interface, is it a good name, structure?
2. Right now each amendment modification triggers the unregistering of all
ServiceUserMapping and then registers all back. Do you think that needs to be
optimized?
[1]
https://github.com/mpetria/sling/compare/mpetria:e62a0e94005709357e9a42a2ba526985d4b588a4...307d32bfafb908ae90569ffd200079553ac2a32c
> 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
>
> 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)
