Hi,

I'm sorry, looks like I missed Event#getPath() namespace translation.

But if the listeners really are tied to the session then the API is
quit confusing as
a) the observation manager is obtained from workspace
b) i don't recall either jsr 170 or the jcr api mentioned anything
about unregistering events on session logout.

Also, would it be a performance problem leaving a session for each
workspace opened to get the proper notifications? There could be
hundreds of sessions opened for each node, but the sessions would be
quite idle and shouldn't hold any transient data.

Kind regards,
-Matej

On Sun, Jul 13, 2008 at 12:29 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Sun, Jul 13, 2008 at 1:06 AM, Matej Knopp <[EMAIL PROTECTED]> wrote:
>> Can anyone explain me why the event observation listeners are removed
>> in session.logout()?
>
> Because they were registered within the scope of that session, and are
> tied to the access credentials and namespace mappings associated with
> that session.
>
> BR,
>
> Jukka Zitting
>

Reply via email to