[
https://issues.apache.org/jira/browse/SLING-13146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-13146.
------------------------------------
Resolution: Fixed
* master:
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/8b524878853dfed07303807bbd555e956526396d
* 3.x:
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/c0464b18d3fab073eddac99b064921bd84a87cfa
> ThreadsafeMockAdapterManagerWrapper: Adapters from test class cannot be found
> -----------------------------------------------------------------------------
>
> Key: SLING-13146
> URL: https://issues.apache.org/jira/browse/SLING-13146
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing Sling Mock 4.0.0, Testing Sling Mock 4.0.2,
> Testing Sling Mock 3.6.0, Testing Sling Mock 4.0.4
> Reporter: Henry Kuijpers
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing Sling Mock 3.6.2, Testing Sling Mock 4.0.6
>
>
> When testing an OSGi service with ResourceResolverType=JCR_OAK, that is (for
> example) a ResourceChangeListener, the following could occur:
> # Test class registers an adapter
> # onChange gets triggered on a different thread, which causes:
> [pool-6-thread-1] WARN
> org.apache.sling.testing.mock.sling.ThreadsafeMockAdapterManagerWrapper -
> Create new bundle context for adapter manager because it was null,
> bundleContext=null
> # The adapterfactories are not there in this new AdapterManager
> # The adaptTo-call returns null
> # When manually triggering the onChange-method from the test, the
> adaptTo-call works, as it uses a different AdapterManager that *does* have
> the adapterfactory
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
