Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAPr=90P=KT-e+a4kr7wxG21sWMc4EXK0Y=xR45rSadqwE3RW=Q@mail.gmail.com>
References: 
 <CAEWfVJmtTF2p8QcMm+AdFd=sZkXH7tF2+sUHdCB7oYr1=-x39g@mail.gmail.com>
	<F9378547-8AAE-4D77-BF9E-6C48A926572E@yahoo.com>
	<CAEWfVJm04pSn5UmcDVJ2L2Se0KPaaUOPyNzKSHasc6qvKc5nYA@mail.gmail.com>
	<CAPr=90P=KT-e+a4kr7wxG21sWMc4EXK0Y=xR45rSadqwE3RW=Q@mail.gmail.com>
Date: Wed, 19 Mar 2014 12:25:47 +0100
Message-ID: 
 <CAEWfVJn1kxK--sFLUn1d5Dh46a=QR-PFRTXrquEcnUYBA=oaZQ@mail.gmail.com>
Subject: Re: How to use a service immediately after its activation?
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: users@felix.apache.org
Content-Type: text/plain; charset=UTF-8

Hi,

On Tue, Mar 18, 2014 at 10:22 PM, Neil Bartlett <njbartlett@gmail.com> wrote:
> ...Whatever you're trying to do in your special listener, wouldn't it be
> better done inside the same bundle as the service?...

You're right, and this is similar to what Bruce suggests - the
bundle's initialization code can look for initializer services using a
whiteboard pattern, and call them before making the actual service
available.

To answer Marcel's question about the use case, the app in question is
Sling-based and uses a content repository service. When upgrading the
app you might need to make some changes to the content before the new
version of the app starts working with the content repository. So yes,
making this part of the content repository service design makes
absolute sense.

David B's hooks suggestion also looks interesting, as a generic way of
talking to services early in the setup phase.

Thanks everybody for the pointers!

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org