On Wed, Apr 23, 2008 at 2:09 PM, Alexander Klimetschek <[EMAIL PROTECTED]>
wrote:
>
> Am 23.04.2008 um 13:49 schrieb Jukka Zitting:
>
>
> >
> > > @All: Is this a bug? Are there any test cases? WDYT?
> > >
> >
> > No, it's a feature. See ConcurrentNodeModificationTest. See my previous
> message.
> >
>
> I don't mean his original example (where the the modifications and saves
> are not "interleaved"). I meant the second one, which Stefan and me pointed
> out:
>
> n1.getNode("jcr:content").setProperty("jcr:data", testcontent + ", as
> modified by session 1");
>
> n2.getNode("jcr:content").setProperty("jcr:data", testcontent + ", as
> modified by session 2");
> n2.save();
> n1.save();
>
> According to Julian, it does not throw an exception for him. Which is a
> bug.
it does throw an exception in my case.
cheers
stefan
>
>
>
> Alex
>
> --
> Alexander Klimetschek
> [EMAIL PROTECTED]
>
> >> Day JCR Cup 08 | Win a MacBook Pro: http://dev.day.com/ <<
>
>
>
>
>
