jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabián Mandelbaum <fmandelb...@gmail.com>
Subject Re: Jackrabbit bug or intended behaviour?
Date Tue, 26 Apr 2011 14:11:32 GMT
On Tue, Apr 26, 2011 at 10:03 AM, Jukka Zitting <jzitting@adobe.com> wrote:
> Hi,
> On 21.04.2011 22:46, Fabián Mandelbaum wrote:
>> I expect each revision to have jcr:lastModifiedBy set to the user
>> owning the R/W session when storing the file, not to the creator of
>> the 1st revision.
>> Are my expectations wrong? Bug or feature? (If it's a feature, what
>> should I do before/after creating the revision to have
>> jcr:lastModifiedBy properly set on each revision?)
> It's a feature. The jcr:lastModifiedBy property is not automatically
> updated by the repository, so you'll need to explicitly set it to a new
> value when you want it to change.
> --
> Jukka Zitting

Well indeed it solved the issue. I've just set the jcr:content node's
jcr:lastModifiedBy property and now the revision author is properly
marked on checkin. Thanks Jukka!

Fabián Mandelbaum
IS Engineer

View raw message