Bug in restoreBaseVersion 2.8.0

[hsp <pi...@ibest.com.br>]

Hi;

Testing a routine to update a recently property we have added in node of
certain nodetype, I have found that some nodes got a update time value in
jcr:created property.
Digging, I found that the nodes were in repository since it was 1.4 jack
(nowadays already migrated to jack 2.8 repository) and not had the
jcr:createdBy property.
These nodes are with mix:versionable too, and in the call to
versionManager.restore(versionManager.getBaseVersion(node.getPath()), true);
the node was updated in jcr:createdBy (with the user in the session) and in
jcr:created property with the time in that moment.
Well, these nodes were created 2 or 3 years ago, so that is embarrasing to
explain to consumers what could happened with they...

I think it is a bug. The scenario it happens is when a node does not have
the jcr:createdBy property, and in the call to restoreVersion the update in
jcr:created is done.

I wont put the update in production environment before assure that the
jcr:created property will not be modified, or a way to put back the value in
it. But I need to trigger this as soon as possible, due to new features and
some speed in existent routines.

I noticed that posts on this forum seem to be abandoned, I hope to have an
answer in a timely manner

<poorenglish>sorry</poorenglish>
Regards,
Helio.



--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Bug-in-restoreBaseVersion-2-8-0-tp4661807.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.