Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of michael.e.harris@gmail.com
 designates 216.239.58.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=mY7yoBxbdwJ9HQry0rBr8VOKMhTIPqYbIz8GVaenFgcatX5Klv4hvyFbxLamdzYCrV
         L5KMMeg6z6iqA1U8J9Is4fnnhsbmly9NBeNdCXLaNE3Asbb5GNBze0HVojozM8dSjjg7
         Guh3PxWaKTx/Bq0jt8LPgC2dF3Z5Lf2V9FdFg=
Message-ID: <82670ba40807210800k66899cc9k67650bc482becda@mail.gmail.com>
Date: Mon, 21 Jul 2008 11:00:49 -0400
From: "Michael Harris" <michael.e.harris@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: newb transient repository questions
In-Reply-To: <488443C3.3070109@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_38876_7570613.1216652449320"
References: <82670ba40807180622j600c5461mf4bf311a67f241ec@mail.gmail.com>
	 <c3ac3bad0807180733g30e7638frcf18aed9cc12a15b@mail.gmail.com>
	 <82670ba40807180740o42a75384m21d303c35ce54c03@mail.gmail.com>
	 <82670ba40807180759l69c8e763g398d10f8399088b8@mail.gmail.com>
	 <488435BC.3060108@gmx.net> <11910710527.20080721092059@holeczek.de>
	 <488443C3.3070109@gmx.net>

------=_Part_38876_7570613.1216652449320
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

So I ran my tests a bunch of times without the delete code.  asset[x]
instances accumulated.  I then tried adding the cleanup code in and thought
that it wasn't cleaning up.

however, I deleted the repo root, and now when i run the tests they clean
up.  So the problem has gone away....

On Mon, Jul 21, 2008 at 4:07 AM, Marcel Reutegger <marcel.reutegger@gmx.net=
>
wrote:

> Hi Florian,
>
> ah, of course, you are right.
>
> Michael, can you tell us what nodes remain in the workspace after you
> removed the assets node and called save?
>
> regards
>  marcel
>
>
> Florian Holeczek wrote:
>
>> Hallo Marcel,
>>
>> are you sure about this? I thought Michael's code produced the
>> following tree:
>>
>>      root
>>       |
>>     assets
>>    /      \
>> asset[1] asset[2]
>>
>> Regards,
>>  Florian
>>
>> Urspr=FCngliche Nachricht vom 21.07.2008 um 09:07:
>>
>>> Hi Michael,
>>>
>>
>>  Michael Harris wrote:
>>>
>>>> another noob question.  I have the following codes
>>>>
>>>>                Node root =3D session.getRootNode();
>>>>                Node assets =3D root.addNode("assets");
>>>>
>>>>                // Store content
>>>>                Node asset =3D assets.addNode("asset");
>>>>                asset.setProperty("url", "http://asset1url.org");
>>>>                asset.setProperty("name", "Asset 1");
>>>>                asset.setProperty("typetype", "image");
>>>>
>>>>                Node asset2 =3D assets.addNode("asset");
>>>>
>>>
>>  this creates a same named sibling /asset[2]
>>>
>>
>>                 asset2.setProperty("url", "http://asset2url.org");
>>>>                asset2.setProperty("name", "Asset 2");
>>>>                asset2.setProperty("type", "image");
>>>>                session.save();
>>>>
>>>> and then
>>>>
>>>>        Node root =3D session.getRootNode();
>>>>        Node assets =3D root.getNode("assets");
>>>>
>>>
>>  this will only return the first asset node but not the second one.
>>>
>>
>>         assets.remove();
>>>>        session.save();
>>>>
>>>> the more I run the test, the more nodes I get.  Seems like the data in
>>>> the
>>>> TransientRepo is being stored on the disk.  The remove is not cleaning
>>>> it
>>>> up.  For why?
>>>>
>>>
>>  to remove all asset nodes you need to do the following:
>>>
>>
>>  for (NodeIterator assets =3D root.getNodes("assets"); assets.hasNext();=
 ) {
>>>     assets.nextNode().remove();
>>> }
>>> session.save();
>>>
>>
>>  regards
>>>  marcel
>>>
>>
>>
>


--=20
---------------------
Michael Harris

------=_Part_38876_7570613.1216652449320--