Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: neutral (nike.apache.org: 195.39.10.3 is neither permitted nor
 denied by domain of vkrejcirik@gmail.com)
Message-ID: <49BE1F80.3010303@gmail.com>
Date: Mon, 16 Mar 2009 10:44:32 +0100
From: vkrejcirik <vkrejcirik@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: dev@jackrabbit.apache.org
Subject: Re: eventListener doesn't work
References: <49B55E4C.70405@gmail.com>
	 <F4259BFD-3CC7-4DBF-8058-66E4CD85D293@tfd.co.uk>
	 <49BD258E.6010803@gmail.com>
 <c3ac3bad0903151359t2912acd1wab130f5ceedc686a@mail.gmail.com>
In-Reply-To: <c3ac3bad0903151359t2912acd1wab130f5ceedc686a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

I have session, where i registered event listener, still open. I have 
another session, where i add nodes and properties. I connect to sling 
repo over rmi, so the session is not in the osgi container.

/**************************************/
Best regards / S pozdravem
Vladislav Krejc(ir(�k

http://www.vkrejcirik.info


Alexander Klimetschek napsal(a):
> On Sun, Mar 15, 2009 at 4:58 PM, vkrejcirik <vkrejcirik@gmail.com> wrote:
>   
>> After registering the event listener I only call session.save(). I don't
>> call close or logout.
>> While changing of property over POST servlet is calling session.save() ?
>>     
>
> If you register the observation listener with the session of the
> request, it will most likely be lost immediately after the request is
> done, as Sling's session pool (is it still active?) will log out the
> session. For observation listeners you should have a OSGi service that
> creates its own session for the event listener and keeps that session
> open as long as the component is active. Often you want an
> administrative session which you can get with an scr reference to the
> SlingRepository and call loginAdministrative() on that.
>
> BTW, you don't need to call save after registering the event listener
> - save is only there to persist changes in nodes or properties.
>
> Regards,
> Alex
>
>