Re: Export content as JSON ready to be imported

Hi Guillaume AFAIK Jackrabbit FileVault uses a similar approach. I'm not super familiar with the code, but you may find interesting details if you look at the classes JackrabbitACLImporter[0] and/or JcrACLManagement[1]. The order of ACEs is significant. IIRC later entries "override" earlier ones

Re: Export content as JSON ready to be imported

Hello Bertrand, Thank you for your reply. I have created SLING-6738 for the ACLs import. Before adding unit tests and sending a PR, I would like to know if I'm going in the right direction. I've seen that in JsonReader there are already createAce and createAcl methods, but they are used to

Re: Export content as JSON ready to be imported

Hi, On Tue, Mar 28, 2017 at 11:25 AM, Guillaume Lucazeau wrote: > ...Considering the lack of responses, Re-importing exported JSON, including > the priviliges, doesn't seem to be a feature that lots of people need, so I > will try to patch the importer on my own :).. I

Re: Export content as JSON ready to be imported

Hello, So I've realized my previous question was dumb, ACLs always get returned when you provide a depth to the JSON servlet... Considering the lack of responses, Re-importing exported JSON, including the priviliges, doesn't seem to be a feature that lots of people need, so I will try to patch

Re: Export content as JSON ready to be imported

Hello, I'm having troubles finding where I should handle ACLs nodes. In your first e-mail you said > Not sure about ACLs though, it seems like they should be handled by the content importer. >From what I see the content importer is the main entry point for content import and is handling JSON or

Re: Export content as JSON ready to be imported

I have created this ticket, for protected properties and nodes: https://issues.apache.org/jira/browse/SLING-6614 I have realized after my previous e-mail that autocreated properties would actually be there after node creation and that I could check their protected status. I have created this PR:

Re: Export content as JSON ready to be imported

Hi Guillaume, On Mon, 2017-03-06 at 12:20 +0100, Guillaume Lucazeau wrote: > Hello Robert, > > I finally have time this week to work on those enhancements, required > on > our project. How does it work, should I create tickets in Sling Jira > and > put a comment saying that i'm trying to fix

Re: Export content as JSON ready to be imported

Hello Robert, I finally have time this week to work on those enhancements, required on our project. How does it work, should I create tickets in Sling Jira and put a comment saying that i'm trying to fix this? I have a question regarding your previous answer: how will this work for new

Re: Export content as JSON ready to be imported

On Wed, 2016-12-21 at 12:30 +0100, Guillaume Lucazeau wrote: > Hello Robert, > > Is it something that would be valuable to Sling itself, or should I > try to > do it just for my project? Enhancements to the content loader are more than welcome in Sling :-) > I couldn't find a list of all

Re: Export content as JSON ready to be imported

Hello Robert, Is it something that would be valuable to Sling itself, or should I try to do it just for my project? I couldn't find a list of all protected properties in Jackrabbit, do you know if there is one? Or maybe there is a way to dynamically know if a property is protected Thank you

Re: Export content as JSON ready to be imported

Hi Guillaume, On Tue, 2016-11-29 at 18:36 +0100, Guillaume Lucazeau wrote: > Hello, > > Currently when you get content through the json extension, it > contains > protected properties ("jcr:created", "jcr:createdBy") and permissions > nodes. > > The protected properties prevent the JSON to be

Export content as JSON ready to be imported

Hello, Currently when you get content through the json extension, it contains protected properties ("jcr:created", "jcr:createdBy") and permissions nodes. The protected properties prevent the JSON to be immediately reimported in another repository, and for what I see here [1] permissions are not