Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <28654869.post@talk.nabble.com>
Date: Mon, 24 May 2010 01:53:24 -0700 (PDT)
From: Lukasz Dywicki <lukasz@dywicki.pl>
To: dev@felix.apache.org
Subject: Re: Karaf features improvements
In-Reply-To: <AANLkTinCBFxVglO48OpgKDNO63Y7nUqd8olatkAlBTgA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <28622180.post@talk.nabble.com>
 <AANLkTinQawGoBZhh1vc7xf5kmrO_on_fyl6_05Q8jN8a@mail.gmail.com>
 <28631675.post@talk.nabble.com>
 <AANLkTinCBFxVglO48OpgKDNO63Y7nUqd8olatkAlBTgA@mail.gmail.com>


Ok,
I will write code similar to feature state management (verify
blueprint/spring context state) and bundle monitoring based od feature sets=
.
I can provide patch for these things.

Regards,
Lukasz


gnodet wrote:
>=20
> On Fri, May 21, 2010 at 11:42, Lukasz Dywicki <lukasz@dywicki.pl> wrote:
>>
>> Hello Guillaume,
>>
>> gnodet wrote:
>>>
>>> There is some work going on in the OSGi Alliance about multiple
>>> frameworks in one JVM (see
>>> http://www.osgi.org/Download/File?url=3D/download/osgi-core-4.3-early-d=
raft1.pdf
>>> for more informations). =C2=A0This would enable to have a tree of OSGi
>>> frameworks instead of a single instance and would enable controlled
>>> sharing between a framework and its parent. =C2=A0 =C2=A0 =C2=A0This wo=
uld enable a
>>> controlled level of isolation and could be used to make sure some
>>> features don't interfere with each other. =C2=A0That's one of the reaso=
n
>>> i'm not totally convinced about your proposal. =C2=A0If we'd were to us=
e
>>> nested frameworks, each feature would have its own framework, so that
>>> would not map well to your proposal.
>>>
>> I didn't know that OSGi alliance published new draft so fast.
>>
>> I am not familar with current draft - but I found that bundle listeners
>> will
>> be also scoped per framework - so when you'll install feature (and
>> budnles)
>> in one other instances will don't know anything about this operation.
>>
>=20
> Well, the idea would be that a feature would create a new nested
> framework, so all features would be visible from the top level.
>=20
>>
>>
>> gnodet wrote:
>>>
>>> The two other things i have in mind for features are:
>>> =C2=A0 * give a lifecycle to a feature (start / stop)
>>> =C2=A0 * allow more control on the bundles when installed (started leve=
l,
>>> start state)
>>>
>>>
>> I agree with you in your proposals:
>> +1 for feature lifecycle
>> +1 allow more control on the bundles when installed
>>
>>
>> gnodet wrote:
>>>
>>> =C2=A0 * leverage obr to compute a transitive closure of the feature be=
fore
>>> installation
>>> The last one would allow a more loose definition of a feature but just
>>> specifying the list of key bundles and let the features service
>>> determine all the required dependencies and download / install them.
>=20
>> I don't know OBR and other stuff so I can't help and vote on this. I can
>> help in first two cases.
>=20
> OBR is a repository containing OSGi metadata.  It would be used to
> compute the required dependencies.
>=20
>>
>>
>> gnodet wrote:
>>>
>>> FWIW, nested frameworks are not available yet in felix (there's only a
>>> prototype in an equinox branch), so we can't really use those now, but
>>> the other things should be possible to implement now. =C2=A0In particul=
ar,
>>> the use of OBR should now be possible since the new release as some
>>> acceptable performances.
>>
>> I think we can leave 4.3 and it's features and make Karaf good base to
>> work
>> with OSGi 4.2.
>> From my side groving osgi complexity it's bad idea - I love KISS
>> principle
>> and in my idea OSGi 4.2 is good example of simple and powerful
>> environment.
>> We should wait until 4.3 will be in final stage to get them into Karaf.
>>
>> Best regards,
>> Lukasz Dywicki
>> --
>> View this message in context:
>> http://old.nabble.com/Karaf-features-improvements-tp28622180p28631675.ht=
ml
>> Sent from the Apache Felix - Dev mailing list archive at Nabble.com.
>>
>>
>=20
>=20
>=20
> --=20
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>=20
>=20

--=20
View this message in context: http://old.nabble.com/Karaf-features-improvem=
ents-tp28622180p28654869.html
Sent from the Apache Felix - Dev mailing list archive at Nabble.com.