Re: upgrade repository structure with backward-incompatible changes

Hi Michael, no mine is not really a problem with the JCR migrator. I needed to update the existing nodes structure to support new functionalities in my application, and to do so I tried to search in internet and read the Oak documentation to understand what was the suggested approach (use the

Re: upgrade repository structure with backward-incompatible changes

Marco, Judging from your original question: is there a problem with the JCR-based approach for migrating the content? If so, can you paste the code and explain what the problem is? Cheers Michael On 19/05/17 09:04, "Julian Sedding" wrote: >Hi Marco > >In this case I

Re: upgrade repository structure with backward-incompatible changes

Hi Marco In this case I think you should use the JCR API to implement your content changes. I am not aware of a pure JCR toolkit that helps with this, so you may just need to write something yourself. Regards Julian On Fri, May 19, 2017 at 5:00 PM, Marco Piovesana

Re: upgrade repository structure with backward-incompatible changes

Hi Julian, I meant I'm using Oak not Sing. Yes I'm using JCR API. Marco. On Fri, May 19, 2017 at 2:22 PM, Julian Sedding wrote: > Hi Marco > > On Fri, May 19, 2017 at 2:10 PM, Marco Piovesana > wrote: > > Hi Julian, Michael and Robert > > first of all

Re: upgrade repository structure with backward-incompatible changes

Hi Marco On Fri, May 19, 2017 at 2:10 PM, Marco Piovesana wrote: > Hi Julian, Michael and Robert > first of all thanks for the suggestions. > I'm using Oak directly inside my application, Do you mean you are not using the JCR API? > so I guess the Sling Pipes > are not

Re: upgrade repository structure with backward-incompatible changes

Hi Julian, Michael and Robert first of all thanks for the suggestions. I'm using Oak directly inside my application, so I guess the Sling Pipes are not something I can use, or not? Is the concept of Pipe already defined in some way inside oak? Marco. On Fri, May 19, 2017 at 10:39 AM, Julian

Re: upgrade repository structure with backward-incompatible changes

Hi Marco It sounds like you are dealing with a JCR-based application and thus you should be using the JCR API (directly or indirectly, e.g. via Sling) to change your content. CommitHook is an Oak internal API that does not enforce any JCR semantics. So if you were to go down that route, you

Re: upgrade repository structure with backward-incompatible changes

On Wed, 2017-05-17 at 09:37 +, Michael Marth wrote: > Hi Marco, > > Maybe I don’t understand correctly your use case, but would it be > easier to simply write a script using the JCR API to do the changes > in the repo? > > Michael For bulk operations like that Sling Pipes is also an

Re: upgrade repository structure with backward-incompatible changes

Hi Marco, Maybe I don’t understand correctly your use case, but would it be easier to simply write a script using the JCR API to do the changes in the repo? Michael On 16/05/17 18:33, "Marco Piovesana" wrote: >Hi Tomek, >yes I'm trying to upgrade within the same

Re: upgrade repository structure with backward-incompatible changes

Hi Tomek, yes I'm trying to upgrade within the same repository type but I can decide weather to migrate the repository or not based on what makes the upgrade easier. The CommitHooks can only be used inside an upgrade to a new repository? What is the suggested way to apply backward-incompatible

Re: upgrade repository structure with backward-incompatible changes

Hi Marco, the main purpose of the oak-upgrade is to migrate a Jackrabbit 2 / CRX2 repository into Oak or to migrate one Oak node store (eg. segment) to another (like Mongo). On the other hand, it’s not a good choice to use it for the application upgrades within the same repository type. You