jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peeter Piegaze" <peeter.pieg...@day.com>
Subject Re: Merging non-versionable nodes
Date Fri, 27 Jul 2007 14:50:34 GMT
Hi Tim, Jose,

Thanks for pointing this out. I'll take a look at the issue and get
back to you guys soon.

Cheers,
Peeter

On 7/18/07, Jose Alvarez <jose.mailinglists@gmail.com> wrote:
> Tim Kuchlein <kuchlein <at> gmail.com> writes:
>
> >
> > Hello
> >
> > I am currently having the same issue with merging two workspaces and
> > I noticed that no one has responded to this issue.  I can't see how
> > the algorithm presented in JSR-170 (8.2.10.1) or the newly released
> > JSR-283 could possibly implement the textual description (8.2.10).
> > Nowhere in the algorithm is the merge result of the nearest
> > versionable ancestor taken into consideration.  Specifically the
> > version of doleave(n) that dofail(n, v') calls needs to be altered to
> > read:
> >
> >       doLeave(n)
> >         for each versionable child node c of n domerge(c).
> >
> > rather than what is currently has:
> >
> >       doLeave(n)
> >         for each child node c of n domerge(c).
> >
> > thanks in advance
> > tim
> >
>
> Hi,
>
> I have found the same issue  in my current project.
> This issue make me think that I don't understand correctly the JCR
> specification about how to merge nodes.
>
> Can someone explain that?
>
> Thanks in advance
>
>
>
>


-- 
Peeter Piegaze

Day Software
Suite 331
67 Mowat Avenue
Toronto Ontario M6K 3E3
Canada

office +1 416 987 5720
mobile +1 647 205 2403
fax +1 866 719 3988

Mime
View raw message