Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
1.0
-
None
-
magnolia-community-webapp, 5.4.4-SNAPSHOT, OS-X
-
-
Empty show more show less
-
Kromeriz 31
-
3
Description
To reproduce:
I: Start with vanilla webapp. (Make sure it does not contain new jcr-tools module.) Create a new role. (E.g. duplicate the "rest" role and change some access rules and rename it to "rest-products").
Export the role with the "old" tool.
II: Start with vanilla webapp and make sure it contains the jcr-tools module (which also will remove (or hide?) the legacy app). This time let the new webapp import the bootsstrap created on step I or create the role again.
Export it with the jcr-tools.
III: Compare the 2 files! There is a bunch of differences. The most significant prbly. at the very top:
old approach, 1st line after <?xml version="1.0" encoding="UTF-8"?>
<sv:node sv:name="rest-products" xmlns:sv="http://www.jcp.org/jcr/sv/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
new approach, 1st line after <?xml version="1.0" encoding="UTF-8"?>
<sv:node sv:name="jcr:root" xmlns:sv="http://www.jcp.org/jcr/sv/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Checklists
Acceptance criteria