it.core.ItemImpl.perform(ItemImpl.java:91)
>>
>> at org.apache.jackrabbit.core.ItemImpl.remove(ItemImpl.java:322)
>>
>> at com.calenco.core.robot.JcrHistoryCleanerTimerTask.processNod
>> e(JcrHistoryCleanerTimerTask.java:75)
>>
>> at com.calenco.core.r
at (soundly, but won't let me remove what I need) the
tree under /jcr:system/jcr:versionStorage is protected in a way that
some of the "regular" node manipulation API (node.remove()) cannot be
used on those nodes.
...
What type of node are you trying to delete? The version history node?
Best regards, Julian
0 -
Finished repository garbage collection.
Then stopped the application and used the tool to inspect the repository...
I still find the orphan version history nodes, which take up useless disk
space and all their references are actually pointing nowhere (to no stored
node, that's what defi
On 2018-03-15 11:47, Fabián Mandelbaum wrote:
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.
Thanks.
Nothing happens with the tree, OK, but is it eligible to be
garbage-collected or not?
I woul
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.
>
>
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?
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
from other libs/frameworks I use) uses version history tracking of items
stored under certain paths.
One of the features of the application
sions-from-Version-History-tp4665744.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
o-you-restore-a-versioned-node-in-a-jackrabbit-2-1-repository
>> to iterate over all the version history for the workspace, and found the
>> versions that were saved for the nodes that we had deleted. I assume it is
>> the version history that prevents the GC from removing the
of a difference in the repository disk usage. I
followed the steps outlined in
http://stackoverflow.com/questions/3292719/how-do-you-restore-a-versioned-node-in-a-jackrabbit-2-1-repository
to iterate over all the version history for the workspace, and found the
versions that were saved for the
followed the steps outlined in
http://stackoverflow.com/questions/3292719/how-do-you-restore-a-versioned-node-in-a-jackrabbit-2-1-repository
to iterate over all the version history for the workspace, and found the
versions that were saved for the nodes that we had deleted. I assume it is the
To prevent jackrabbit server disk space from filling up too quickly, is there
a configuration or setting we can apply to cap the number of versions that a
node can retain in its version history? Or is this something that will
require programmatic/manual scrubbing?
Thanks,
Chris
--
View this
;>> I have reading
>>>
>>> http://www.day.com/specs/jcr/2.0/15_Versioning.html
>>>
>>> but it's not really clear to me whether it is possible to access the
>>> version history of a deleted node?
>>>
>>> Let's say I am
/15_Versioning.html
but it's not really clear to me whether it is possible to access the
version history of a deleted node?
Let's say I am creating a node at
/foo/bar/hello-world.txt
and edit the content associated with this node several times and hence
create a version history.
At some point I a
ng.html
>>
>> but it's not really clear to me whether it is possible to access the
>> version history of a deleted node?
>>
>> Let's say I am creating a node at
>>
>> /foo/bar/hello-world.txt
>>
>> and edit the content associated with t
On 2014-01-15 20:45, Michael Wechner wrote:
Hi
I have reading
http://www.day.com/specs/jcr/2.0/15_Versioning.html
but it's not really clear to me whether it is possible to access the
version history of a deleted node?
Let's say I am creating a node at
/foo/bar/hello-world.txt
an
Hi
I have reading
http://www.day.com/specs/jcr/2.0/15_Versioning.html
but it's not really clear to me whether it is possible to access the
version history of a deleted node?
Let's say I am creating a node at
/foo/bar/hello-world.txt
and edit the content associated with this no
Hi,
ok I see. If version history has at least one regular version I will check
if node with UUID jrc:versionableUuid exists.
If it does not exist it is orphaned version history and I can remove it by
removing versions from it (from version history).
If version history has only root version
Hi,
removing the last regular version of a version history should remove
the version history. See: https://issues.apache.org/jira/browse/JCR-134
however, there's a special case and an open issue, when only a root version
exists for a versionable node. see:
https://issues.apache.org/jira/b
Hello,
I want to ask if there is any way how to remove unused version history. My
(incorrect used case)
1.Add versionable node.
2.Remove versionable node without removing version history.
I know it is possible to remove version history when I get version history
first from node using
>> }
>>
>>
>>
>> On Tue, May 24, 2011 at 12:34 PM, Raj wrote:
>> > Any pointers would be helpful.
>> >
>> > thanks,
>> > Raj
>> >
>> > On Mon, May 23, 2011 at 2:12 PM, Raj wrote:
>> >
>
}
>}
>}
>
>
>
> On Tue, May 24, 2011 at 12:34 PM, Raj wrote:
> > Any pointers would be helpful.
> >
> > thanks,
> > Raj
> >
> > On Mon, May 23, 2011 at 2:12 PM, Raj wrote:
> >
> >
uld be helpful.
>
> thanks,
> Raj
>
> On Mon, May 23, 2011 at 2:12 PM, Raj wrote:
>
>> hi All,
>>
>> My requirement is to delete the node and its history, as both won't be
>> useful as per application logic.
>> I would like to completel
Any pointers would be helpful.
thanks,
Raj
On Mon, May 23, 2011 at 2:12 PM, Raj wrote:
> hi All,
>
> My requirement is to delete the node and its history, as both won't be
> useful as per application logic.
> I would like to completely delete version history for the node
hi All,
My requirement is to delete the node and its history, as both won't be
useful as per application logic.
I would like to completely delete version history for the node as it will
save us disk space and backup time.
Node childNode = parentNode.getNode("mynode")
Hi,
we do not want to change the latest revision. We want to change the complete
version history and all versions (revisions) in there because we have to
migrate some data. I think that is not possible because Jackrabbit throws a
Exception when you try to change a version node from version
; Hi all,
>
>
>
> is it possible to change some properties on a already checked in node? I
> mean when I create a node that is versionable and create a version of
> this node in the version history with some properties, is it then
> possible to change the properties of the version
Hi all,
is it possible to change some properties on a already checked in node? I
mean when I create a node that is versionable and create a version of
this node in the version history with some properties, is it then
possible to change the properties of the version node in the version
history
Thank you so much Thomas.
Ich wünsche dir einen schönen Tag ;-)
Hi,
> should obtain it from VersionManager or something like this, but don't
> know how!!
See
http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/javax/jcr/version/VersionManager.html
"The VersionManager object is accessed via
Workspace.getVersionManager()." and "The Workspace object can be
acqu
Hi,
Please, can any one guide me how to obtain the VersionHistory of a node in
Jackrabbit 2.0?
Here's the code how I used to obtain it in the previous release:
VersionHistory versionIterator = node.getVersionHistory();
while(versionIterator.hasNext()){
Version version = versionIterator.
Hi!
I'm using Jackrabbit 1.4.x and trying to access child nodes by using OCM.
The code is somewhat as below:
VersionedDocument document = (VersionedDocument)
ocm.getObject(orginalDocument.getPath(), version);
String data = null;
try {
Resource r = document.get
hi,
versions are shared amongst all workspaces. this is intentionally so
that corresponding nodes can checkin/checkout/restore/merge from their
common version.
if you need/want to remember the versions origin, you need to set it
manually on a property before your do the checkin.
regards, toby
On
Hi,
Is there any way one can determine what workspace a version belongs to?
If we have multiple workspaces configured (in case of branching), the
history view will show all the versions present in multiple workspace. Is
there a way we can determine which version belongs to which workspace???
Than
Hello,
How can export the version history? if for example coron.jpg has has version
1.0, 1.1, 1.2, as per my testing the latest version exported. How can export
the old version?
thanks a lot.
cheers.
--
View this message in context:
http://www.nabble.com/Export-version-history
nterest in this solution.
--
View this message in context:
http://www.nabble.com/Deleting-a-node-also-delete-version-history-of-the-node-tp18104105p18221650.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
--
Cédric Damioli
Responsable produit Ametys
So
would create a lot
> of really unused data on the disk), you might consider not to version
> them at all.
>
> Regards,
> Alex
>
> On Tue, Jul 1, 2008 at 7:53 PM, hsp_ wrote:
>>
>> Hi, I also have interest in this solution.
>>
>> --
>> View this me
Done : https://issues.apache.org/jira/browse/JCR-1973
Regards,
Gerald Reinhart
--
View this message in context:
http://www.nabble.com/OCM%2C-queries-and-version-history-tp21459838p21934062.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
in a couple of days.
Best regards,
Christophe
>
> --
> View this message in context:
> http://www.nabble.com/OCM%2C-queries-and-version-history-tp21459838p21918082.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>
teFilter(MyObject.class
);
filterChange.setScope( "/jcr:system/jcr:versionStrorage//");
--
View this message in context:
http://www.nabble.com/OCM%2C-queries-and-version-history-tp21459838p21918082.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Hi,
Searching objects in the version history is not yet supported. For the
moment, you can only get the version history and loop on the different
versions (see the unit test AnnotationBasicVersionningTest).
There is a workaround but this is not the ideal solution :
Make your own jcr query to get
Hi again,
it's possible to search an object by the value of an attribute thought
the version history?
Ok, let me to better explain it; I have an object like this (correctly
mapped in a xml descriptor and defined (CND) - it has the
"mix:versionable" type too):
public
ave to first delete the node and then its versions.
>>>> For this you need to store the version history before deleting the node.
>>>> Indeed, if you delete the node you cannot access the version history
>>>> anymore.
>>>>
>>>> Here an
On Tue, Jan 6, 2009 at 11:55 AM, Sébastien Launay
wrote:
> Alexandru Popescu ☀ a écrit :
>> On Mon, Jan 5, 2009 at 11:19 PM, Sébastien Launay
>> wrote:
>>
>>> You have to first delete the node and then its versions.
>>> For this you need to store the v
Alexandru Popescu ☀ a écrit :
> On Mon, Jan 5, 2009 at 11:19 PM, Sébastien Launay
> wrote:
>
>> You have to first delete the node and then its versions.
>> For this you need to store the version history before deleting the node.
>> Indeed, if you delete the node yo
On Mon, Jan 5, 2009 at 11:19 PM, Sébastien Launay
wrote:
> You have to first delete the node and then its versions.
> For this you need to store the version history before deleting the node.
> Indeed, if you delete the node you cannot access the version history
> anymore.
>
&g
You have to first delete the node and then its versions.
For this you need to store the version history before deleting the node.
Indeed, if you delete the node you cannot access the version history
anymore.
Here an example, from JCR-134 test case:
Node n = rootNode.addNode("test");
> - after 3 years we deleted the content (the node and then its remaining
> versions)
>
> Because, the node is deleted but its empty version history is still
> present in Jackrabbit storage, the disk usage continues to grow.
> The goal of the purge was precisely to have a const
empty version history is still
present in Jackrabbit storage, the disk usage continues to grow.
The goal of the purge was precisely to have a constant disk usage
because the content creation throughput is constant (i.e. after 3
years of production the number of nodes must have reached a
maximum).
I
how can I restore some information about a node after it being deleted? how
i get a reference for your version history?
2009/1/5 Tako Schotanus
> IMO this is because versioning is not seen as a method to go back to older
> version for isolated files but as a way to get a "snapshot&qu
on versioning makes sense when we wanna
> modify a file and may wanna restore the previous file versions in the
> future.
> When we delete a file, we don't think of restoring previous file versions.
> Moreover, deleting a node(representing a file) we won't get a reference for
> your version history, then why should we keep the version history of this
> node?
>
storing previous file versions.
Moreover, deleting a node(representing a file) we won't get a reference for
your version history, then why should we keep the version history of this
node?
nother repo, and then the
version-history was lost.
i had to write the workspace again, but with large binary data i could
not use the import/export mechanism of jackrabbit and i had to do it
manually - this was pain.
i would be very interested in a better solution too.
greetings
felix
Tamara
another repo, and then the
version-history was lost.
i had to write the workspace again, but with large binary data i could
not use the import/export mechanism of jackrabbit and i had to do it
manually - this was pain.
i would be very interested in a better solution too.
greetings
felix
Hi all,
I have had this problem too, those nodes were read-only after i transferred the
workspace to another repo, and then the version-history was lost.
i had to write the workspace again, but with large binary data i could not use
the import/export mechanism of jackrabbit and i had to do
I lost the versionHistory node from several nodes and now isn't possible
to remove these nodes.
I would like to know how can I remove these nodes or rebuild the
versionHistory nodes.
Thanks in advance,
Tamara Coutinho
> wrote:
>
> Hi, I also have interest in this solution.
>
> --
> View this message in context:
> http://www.nabble.com/Deleting-a-node-also-delete-version-history-of-the-node-tp18104105p18221650.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.co
Hi, I also have interest in this solution.
--
View this message in context:
http://www.nabble.com/Deleting-a-node-also-delete-version-history-of-the-node-tp18104105p18221650.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
version has the uuid of the root version as its predecessor. Since a
reference is existing i am unable to delete each of them and it gives me a
Referential Integrity Exception.
I tried using node.removeMixin() but that only removes the reference of the
version history from the actual node and does not
On Tue, Jun 24, 2008 at 11:02 PM, Pulla Venkat <[EMAIL PROTECTED]> wrote:
> what should I do to delete version history also ?
Call VersionHistory.removeVersion() for each version.
Regards,
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
Hi,
I am trying to understand the node deletion in jackrabbit. we have scenarios
for deleting nodes which should delete version history associated with the
node.
Node.remove() -- Method in javax.jcr.Item Interface [ inherited by
javax.jcr.Node interface ]
Does the above method remove the
hi paco,
> > i think the version history is not affected if you make changes
> > to your node types.
> This is not always true. I'have added an "user comment" property to the
> versioned node, so the applications expect to see this property in the
> versi
change my node type configuration and want to
> > preserve the node version history?
>
> The easiest way to achieve that at the moment is probably to update
> the namespace of the node types in question so you can keep both the
> old and the new types in the same repository and migr
El mar, 11-03-2008 a las 12:07 +0100, David Nuescheler escribió:
> hi paco,
>
> i think the version history is not affected if you make changes
> to your node types.
This is not always true. I'have added an "user comment" property to the
versioned node, so the appl
hi paco,
i think the version history is not affected if you make changes
to your node types.
generally the version store is implemented as a workspace so you can
just copy the version store on to your new repository, but you need
to make sure that the uuid's (and version property) of the
Hi,
On Tue, Mar 11, 2008 at 12:58 PM, Paco Avila <[EMAIL PROTECTED]> wrote:
> I've posted this message a week ago and nobody tell anything about it.
>
> What can I do if i need to change my node type configuration and want to
> preserve the node version history?
The easi
I've posted this message a week ago and nobody tell anything about it.
What can I do if i need to change my node type configuration and want to
preserve the node version history?
I can't belibe nobody have this problem!
--
Paco Avila <[EMAIL PROTECTED]>
GIT Consultors
t; >> What's your use case for wanting to get the version history of a
> >> removed node?
> >
> > On a more theoretical level: isn't this a limitation of the spec? By
> > the time you remove the event the path information attached to the
> > event
rabbit-core/src/main/config/repository.xml
It's at the very end of the file.
regards
marcel
Bob Wieler wrote:
> The version workspace configuration we're using is:
>
>
>
>
>
>
>
>
> I'm not sure what else would need to be config
The version workspace configuration we're using is:
I'm not sure what else would need to be configured to allow me to search
through the version history node.
Thank you for your help,
Bob
On 5/10/07, harvey waters <[EMAIL PROTECTED]> wrote:
Just a thought, bu
The version workspace configuration we're using is:
I'm not sure what else would need to be configured to allow me to search
through the version history node.
Thank you for your help,
Bob
On 5/10/07, harvey waters <[EMAIL PROTECTED]> wrote:
Just a t
Just a thought, but have you set up the Version workspace index settings ?
On 5/9/07, Bob Wieler <[EMAIL PROTECTED]> wrote:
-- Forwarded message --
From: Bob Wieler <[EMAIL PROTECTED]>
Date: May 9, 2007 5:11 PM
Subject: XPath queries on version history nod
-- Forwarded message --
From: Bob Wieler <[EMAIL PROTECTED]>
Date: May 9, 2007 5:11 PM
Subject: XPath queries on version history nodes
To: users@jackrabbit.apache.org
I'm trying to write an XPath query (Jackrabbit version 1.3) that will find
all of the jcr:versionLabe
Alexandru Popescu wrote:
What's your use case for wanting to get the version history of a
removed node?
On a more theoretical level: isn't this a limitation of the spec? By
the time you remove the event the path information attached to the
event is quite useless, so the mechanism sho
perty set inside
jcr:content). So when i update or add new nt:file node, I can always read
those custom property which decides whether to publish the file on the file
system.
I was assuming that the version history still remains intact eventhough you
remove the versionable node from the repository.
On 4/11/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 4/10/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
> On a more theoretical level: isn't this a limitation of the spec? By
> the time you remove the event the path information attached to the
> event is quite useless, so the mechani
y.
So when i get an event for NODE_REMOVED, I need to pull out the property set
on jcr:content node of the deleted node. I had a notion that the version
history still remains eventhough you remove the node from the repository.
Now my problem is to get a handle to jcr:content node and do some proc
Hi,
On 4/10/07, Alexandru Popescu ☀ <[EMAIL PROTECTED]> wrote:
On a more theoretical level: isn't this a limitation of the spec? By
the time you remove the event the path information attached to the
event is quite useless, so the mechanism should try to publish more
usefull information.
I thin
the repository.
So when i get an event for NODE_REMOVED, I need to pull out the property set
on jcr:content node of the deleted node. I had a notion that the version
history still remains eventhough you remove the node from the repository.
Now my problem is to get a handle to jcr:content node and do
What's your use case for wanting to get the version history of a removed node?
On a more theoretical level: isn't this a limitation of the spec? By
the time you remove the event the path information attached to the
event is quite useless, so the mechanism should try to publish more
use
re any thing i am doing wrong here. let me know.
Casting the event to EventImpl only works when you're using a local
Jackrabbit instance, not when using Jackrabbit remotely over the RMI
layer.
What's your use case for wanting to get the version history of a removed node?
BR,
Jukka Zitting
doing wrong here. let me know.
thanks,
Sudhan
Tobias Bocanegra wrote:
>
> hi,
> unfortunately, the event for the node_removed does not contain any
> suitable information by the path anymore. what you need is the uuid of
> the node, in order to get the version history.
>
&
hi,
unfortunately, the event for the node_removed does not contain any
suitable information by the path anymore. what you need is the uuid of
the node, in order to get the version history.
if you run inside jackrabbit, you can cast the Event to EventImpl, and
then fetch the "NodeId getPar
I am having trouble in getting the version history once I delete the node
through DavExplorer.
I have listeners like this :
1) This is used for listening to any nodes created or updated on version
storage
session.getWorkspace().getObservationManager().addEventListener
Makes sense. Thanks!
Jukka Zitting-3 wrote:
>
> Hi,
>
> On 11/2/06, James Hang <[EMAIL PROTECTED]> wrote:
>> I noticed that when traversing a node's version history by calling
>> Node.getVersionHistory(), the versions returned contains paths and node
Hi,
On 11/2/06, James Hang <[EMAIL PROTECTED]> wrote:
I noticed that when traversing a node's version history by calling
Node.getVersionHistory(), the versions returned contains paths and node
types of the node in the version workspace, not in the workspace of the node
that was ver
I noticed that when traversing a node's version history by calling
Node.getVersionHistory(), the versions returned contains paths and node
types of the node in the version workspace, not in the workspace of the node
that was versioned. So calling Version.getPath() returns something
Shanmugam Gopal wrote:
Can I have sample code for creating custom nodes like extending nt:file
and nt:unstructured node types?
yes, you can. See the documentation:
http://jackrabbit.apache.org/doc/nodetype/index.html
regards
marcel
Hi,
Can I have sample code for creating custom nodes like extending nt:file and
nt:unstructured node types?
regards,
Shanmugam G
From: Marcel Reutegger <[EMAIL PROTECTED]>
Reply-To: users@jackrabbit.apache.org
To: users@jackrabbit.apache.org
Subject: Re: File node - Version Histor
ge as well.
regards
marcel
Shanmugam Gopal wrote:
Hi,
I have created a file node in repository. Different users can check
out and check in this file.
At any point of time, I should get the version history like version
name, version created time and the user who has created that
particular versi
Hi,
I have created a file node in repository. Different users can check out and
check in this file.
At any point of time, I should get the version history like version name,
version created time and the user who has created that particular version.
From VersionHistory and Version
Hi,
I have created a file node in repository. Different users can check out and
check in this file.
At any point of time, I should get the version history like version name,
version created time and the user who has created that particular version.
From VersionHistory and Version interfaces
Hi,helper!
Now, I have a problem with JackRabbit API. I don't know how to move
version history from a repository (A) to another (B) and remove this
versision history. I gived a solution but it is not performance:
- Get node from A
- Add node into B
- Get List of versions of node from A
93 matches
Mail list logo
