You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/01/22 12:15:00 UTC

[jira] [Created] (SLING-12237) Extend exception message for RepositoryInitializerFactory with config PID

Konrad Windszus created SLING-12237:
---------------------------------------

             Summary: Extend exception message for RepositoryInitializerFactory with config PID
                 Key: SLING-12237
                 URL: https://issues.apache.org/jira/browse/SLING-12237
             Project: Sling
          Issue Type: Improvement
          Components: Repoinit
    Affects Versions: Repoinit JCR 1.1.46
            Reporter: Konrad Windszus
             Fix For: Repoinit JCR 1.1.48


Currently an error in any of the repoinit scripts or reference just lead to an exception which does not expose the configuration PID triggering the exception, e.g.

{code}
javax.jcr.RepositoryException: Applying repoinit operation failed despite retry; set loglevel to DEBUG to see all exceptions. Last exception message was: Session.save failed: javax.jcr.nodetype.ConstraintViolationException: OakConstraint0001: /var/groovyconsole[[nt:folder]]: No matching definition found for child node audit with effective type [nt:unstructured]
  at org.apache.sling.jcr.repoinit.impl.RepositoryInitializerFactory.applyOperations(RepositoryInitializerFactory.java:176) [org.apache.sling.jcr.repoinit:1.1.38]
{code}

As repo init scripts are contributed by many different suppliers the underlying configuration PID should be contained in the exception message as well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)