Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <14033021.post@talk.nabble.com>
Date: Thu, 29 Nov 2007 11:22:27 -0800 (PST)
From: qcfireball <qcfireball@yahoo.com>
To: users@jackrabbit.apache.org
Subject: RMI Observation
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I noticed that when registering a new Observer via RMI, if I do not provide a
"thread trick" the Thread immediately dies, and the Observer with it.

Basically I am synchronizing on an arbitrary Object, then calling 'wait'. 
Not a very nice solution, but it works for now.  Seems like a hack to me.

I guess it makes sense that the Thread would immediately die without some
kind of effert.  I am wondering how other people are making sure that their
Observer does not die?  Are there ways that are preferred over others?

Is this behavior going to be the same when registering an Observer within a
web container, directly using the Jackrabbit API's?
-- 
View this message in context: http://www.nabble.com/RMI-Observation-tf4899371.html#a14033021
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.