[SLING-8843] Repoinit developer mode: relax constraints on SlingRepository service creation

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Repoinit JCR 1.1.14
• Component/s: Repoinit
• Assignee: Joerg Hoh
• Reporter: Joerg Hoh
• Created: 13/Nov/19 08:32
• Updated: 15/Dec/22 09:13

Description

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.)