[jira] [Created] (SLING-8843) exceptions on repoinit break construction of the SlingRepository service

["Jörg Hoh (Jira)" <ji...@apache.org>]

Jörg Hoh created SLING-8843:
-------------------------------

             Summary: exceptions on repoinit break construction of the SlingRepository service
                 Key: SLING-8843
                 URL: https://issues.apache.org/jira/browse/SLING-8843
             Project: Sling
          Issue Type: Improvement
          Components: Repoinit
    Affects Versions: Repoinit JCR 1.1.14
            Reporter: Jörg Hoh


The repoinit statements are executed during the construction of the SlingRepository instance; and if currently an exception is thrown at that level (for whatever reason), this exception is propagated up to the construction of the SlingRepository service, which is then terminated. As a consequence the SlingRepository is not available which makes the application unusable.

While this should never happen, any occurrence of it makes fixing it harder, especially if the analysis requires to have a look at the content within the repository.

Thus i would request, that all type of exceptions thrown within repoinit are caught and logged, but do not propagated.

(Especially if you play with repoinit statements you have a high chance, that you boostrap your instance multiple times if you don't get it right the first time.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)