You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Julian Sedding (JIRA)" <ji...@apache.org> on 2016/12/15 15:12:58 UTC

[jira] [Created] (SLING-6401) AbstractSlingRepositoryManager should guard against NPE due to async initialization

Julian Sedding created SLING-6401:
-------------------------------------

             Summary: AbstractSlingRepositoryManager should guard against NPE due to async initialization
                 Key: SLING-6401
                 URL: https://issues.apache.org/jira/browse/SLING-6401
             Project: Sling
          Issue Type: Improvement
          Components: JCR
    Affects Versions: JCR Base 3.0.0
            Reporter: Julian Sedding
            Assignee: Julian Sedding
            Priority: Minor


With the asynchronous initialization of the repository it is possible that subclasses or test cases call {{AbstractSlingRepositoryManager#create}} before the repository is fully initialized. This can lead to NPEs. We should guard against this problem.

Note, however, that the {{SlingRepository}} service is only registered *after* the repository is fully initialized. Therefore this issue, which was only observed in a 3rd party test-case, does not impact normal usage in an OSGi container.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)