[
https://issues.apache.org/jira/browse/SLING-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339191#comment-17339191
]
Achim Koch edited comment on SLING-10349 at 5/4/21, 5:52 PM:
-------------------------------------------------------------
I am using the cloud SDK 2021.1.4738.20210107T143101Z
Repoinit is version 1.1.28
Parser is version 1.6.2
The repoinit file in total is pretty large (1500 lines) and cannot be share
here. I can try if the issue occurs in a smaller separate file, too.
The file is not transformed by us.
was (Author: -achim):
I am using the cloud SDK 2021.1.4738.20210107T143101Z
Repoinit is version 1.1.28
Parser is version 1.6.2
The repoinit file in total is pretty large (1500 lines) and cannot be share
here. I can try if the issue occurs in a smaller separate file, too.
> Repoinit: Nodetype definitions not working
> -------------------------------------------
>
> Key: SLING-10349
> URL: https://issues.apache.org/jira/browse/SLING-10349
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Reporter: Achim Koch
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> Tried to register nodetypes and namespaces like so:
> register namespace ( yyy ) http://yyy.com/jcr/nt/1.0
> register nodetypes
> <<===
> << <yyy='http://yyy.com/jcr/nt/1.0'>
> << [yyy:Foobar] > nt:unstructured
> ===>>
> The whole repoinit script was ignored, then. (I created a "marker" with
> createuser that also was not executed).
> I saw no apparent error in the logfile.
> The namespace did register, when I removed the whole "register nodetypes"
> block.
> Btw. the documentation could be more explicit that (if) "<<
> <yyy='http://yyy.com/jcr/nt/1.0'>" already creates a namespace (or if that is
> required to reference an existing one in the scope of the CND block)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
