I'll try to provide the details for dependency hell with 2.6 and other
frameworks/libs later, I'm a bit overloaded with other things now, sorry.

Nothing happens with the tree, OK, but is it eligible to be
garbage-collected or not?

Indeed, if you try to delete a referenced node you get a
ReferentialIntegrityException, which is fine. Now, I'll be fine with
writing a robot (periodically-run task) to find all such orphans and wipe
them. How can I detect those orphans SAFELY (in a way that attempting to
delete them will not throw ReferentialIntegrityException, and will not
break my content repository in any way). Is there a ready-made utility
method in the API or a query, or set of queries, I can run to detect those
orphans?

Thanks again for your help.

Best regards, Fabián

On Thu, Mar 15, 2018 at 7:24 AM, Julian Reschke <[email protected]>
wrote:

> On 2018-03-15 10:47, Fabián Mandelbaum wrote:
>
>> Hello,
>>
>> my application based on JackRabbit 2.x (albeit an old .x, IIRC, .6, still
>> cannot upgrade to latest because it breaks my build... lots of
>> dependencies
>>
>
> Details appreciated. We'll abandon 2.6 this year.
>
> from other libs/frameworks I use) uses version history tracking of items
>> stored under certain paths.
>>
> >
>
>> One of the features of the application is to be able to erase the items
>> (wipe
>> them, and all related nodes and stored information forever) in question.
>>
>> When deleting those items, what happens with their version history tree?
>> Is
>>
>
> By default, nothing. (I think)
>
> the version history tree eligible for garbage collection (ran by a "robot"
>> in my app once a day)? Or should I also delete the version history tree
>> "by
>> hand" (which poses lots of problems with session state... I have to do
>> session.save() 'in the middle' of the deletion process)?
>>
>> Thanks in advance for your answers.
>>
>
> I think you can delete the version history if and only iff there is no
> version controlled node referring to it anymore.
>
> Best regards, Julian
>



-- 
Fabián Mandelbaum
IS Engineer

Reply via email to