Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of bcanhome@googlemail.com
 designates 209.85.161.43 as permitted sender)
Message-ID: <4E1DFBE3.9040804@googlemail.com>
Date: Wed, 13 Jul 2011 22:11:15 +0200
From: Achim Nierbeck <bcanhome@googlemail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de;
 rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: users@felix.apache.org
Subject: Re: Moving fragment to Resolved state in fileinstall watched
 directory?
References: <32052770.post@talk.nabble.com>	<4E1DAFF5.9080309@ungoverned.org>
	<32054785.post@talk.nabble.com>
 <CAAVqk_wYQHZFGXumy3dgN84thRDxgEfX2q1jP_crhj6bNcuBfg@mail.gmail.com>
In-Reply-To: 
 <CAAVqk_wYQHZFGXumy3dgN84thRDxgEfX2q1jP_crhj6bNcuBfg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I might be naive, but I think this would be a great feature for felix.
Often this is a real downside for using fragments that they don't get
attached because the host bundle
is already started, so you start tuning with startlevels which for me is
just a bad workaround.
Would this be a possible enhancement for felix?

regards, Achim

Am 13.07.2011 18:30, schrieb Richard Hall:
> On Wed, Jul 13, 2011 at 12:03 PM, lili_ili <svetloe@gmail.com> wrote:
>
>> Thank you, Richard. Can you recommend a java side solution?
>> I have an "installer" code that copies the fragment to the watched
>> directory. From there, I think to add a listener and after a fragment is
>> started redeploy its host. Is there a simpler solution?
>>
> I'm pretty sure this was some discussion on this exact topic not too long
> ago...
>
> At any rate, you could write a bundle that listens for bundles to be
> installed. It could (after perhaps a short delay) determine if that bundle
> was a fragment and if its matching host was already resolved. If so, it
> could then refresh and/or re-resolve the host, which would most likely
> result in the framework attaching the fragment. If the host is active, then
> refreshing it should be sufficient since it will automatically get
> re-started and re-resolved.
>
> -> richard
>
>
>> thanks again
>>
>>
>> Richard S. Hall wrote:
>>> If the host gets resolved first, then the fragment won't be able to
>>> attach to it since Felix doesn't support dynamic fragment attachment
>>> (and Equinox only supports it in a limited way). The most portable
>>> approach is to make sure the fragment is installed into the framework
>>> before the host is resolved.
>>>
>>> -> richard
>>>
>>> On 7/13/11 10:01, lili_ili wrote:
>>>> Hi
>>>>
>>>> I have a directory being watched by fileinstall. Fragment is copied to
>>>> this
>>>> directory after its host, and it automatically moves to "Installed"
>>>> state.
>>>> To make it "Resolved", I need to either run "resolve X" command, or
>>>> restart
>>>> the server.
>>>> Is there a way to solve it and resolve fragments located in "watched"
>>>> directories?
>>>>
>>>> thank you.
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>>
>> --
>> View this message in context:
>> http://old.nabble.com/Moving-fragment-to-Resolved-state-in-fileinstall-watched-directory--tp32052770p32054785.html
>> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>


-- 
-----

Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>  Committer & Project Lead


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