[jira] [Updated] (SLING-12157) [osgi-mock] late binding does not work for non-service DS components
[
https://issues.apache.org/jira/browse/SLING-12157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-12157:
---
Issue Type: Improvement (was: Task)
> [osgi-mock] late binding does not work for non-service DS components
> -
>
> Key: SLING-12157
> URL: https://issues.apache.org/jira/browse/SLING-12157
> Project: Sling
> Issue Type: Improvement
> Components: Testing
>Affects Versions: Testing OSGi Mock 3.3.10
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Major
> Fix For: Testing OSGi Mock 3.4.0
>
>
> A DS component that is not a service can be "injected" and "activated", but
> if a service becomes available, that satisfies a dynamic reference, the
> "bind" method is not called. The same should be true for the "unbind"
> scenario.
> I observed this when I was registering a {{ResourceDecorator}} service in a
> test case, and it did not get bound by the
> {{ResourceResolverFactoryActivator}} that was already registered by the
> {{SlingContext}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-12157) [osgi-mock] late binding does not work for non-service DS components
[
https://issues.apache.org/jira/browse/SLING-12157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-12157:
---
Fix Version/s: Testing OSGi Mock 3.4.0
> [osgi-mock] late binding does not work for non-service DS components
> -
>
> Key: SLING-12157
> URL: https://issues.apache.org/jira/browse/SLING-12157
> Project: Sling
> Issue Type: Task
> Components: Testing
>Affects Versions: Testing OSGi Mock 3.3.10
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Major
> Fix For: Testing OSGi Mock 3.4.0
>
>
> A DS component that is not a service can be "injected" and "activated", but
> if a service becomes available, that satisfies a dynamic reference, the
> "bind" method is not called. The same should be true for the "unbind"
> scenario.
> I observed this when I was registering a {{ResourceDecorator}} service in a
> test case, and it did not get bound by the
> {{ResourceResolverFactoryActivator}} that was already registered by the
> {{SlingContext}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
