This is an automated email from the ASF dual-hosted git repository.

jsedding pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 7ef9852f0 SLING-12107 - JCR Repoinit executes operations out of order 
(#143)
7ef9852f0 is described below

commit 7ef9852f0d757b6d597c5f745f89af835239505a
Author: Julian Sedding <[email protected]>
AuthorDate: Fri Nov 17 14:07:29 2023 +0100

    SLING-12107 - JCR Repoinit executes operations out of order (#143)
    
    - document execution order of repoinit statements
---
 .../content/documentation/bundles/repository-initialization.md      | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git 
a/src/main/jbake/content/documentation/bundles/repository-initialization.md 
b/src/main/jbake/content/documentation/bundles/repository-initialization.md
index 2b44fac43..68811bdf5 100644
--- a/src/main/jbake/content/documentation/bundles/repository-initialization.md
+++ b/src/main/jbake/content/documentation/bundles/repository-initialization.md
@@ -49,6 +49,12 @@ of the repoinit parser to a JCR repository.
 The language is mostly self-explaining, the test suite listed below in 
Appendix A exposes
 all language constructs and options.
 
+When a repoinit script is applied with the `org.apache.sling.jcr.repoinit` 
module, the execution order of the individual
+statements is slightly different from their order within the script. Namely, 
all statements creating namespaces are
+executed before any other statements. Next, all statements registering 
nodetypes or privileges are executed. And finally,
+all other statements are executed in the order they are defined. This 
reordering is intended to avoid issues due to
+missing namespaces, nodetypes or privileges when content is created. 
+
 ## Validating repoinit statements
 
 There are multiple means to validate the syntax of repoinit statements (only 
leveraging the parser, but not the actual JCR Repoinit implementation) outlined 
below.

Reply via email to