[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] need some help with feature un-installation process.
- From: Pradeep Fernando <pradeepfn@xxxxxxxxx>
- Date: Fri, 19 Nov 2010 11:59:00 +0530
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=s/2bc8IT3tb9VWM95q+UigRESGOhwZld5ir8LYsQy4hB6MgQttiktP6eO09ZgHqhwj 5llKroU6f2Jc6KytQo+gWYYyH5Uj5RaNXQ4vsLT2+ySugYK6rZGn4KWLzWbx/OzNbqOT IHY6U7d+ZuQkAFIiitv3LZlOt/U6Pmv5IrxPA=
I am relatively new to Equinox OSGI & P2 provisioning. My primary
reference is OSGI & Equinox book  . In my current code, I have
features that wraps server side functionality & client side
functionality. In order to create further abstraction I wrap these
features in another composite feature using.
<include/> directive in the feature xml.
The end result is ;
Composite_feature -- --- server feature
'-- ui feature
But with this organization I'm finding it hard to implement a
un-installation, where i can select any of the UI feature & click
In my current code the p2-planner gives a severity status 4. which
says there are other features that depends on the UI feature. This is
acceptable since the
composite feature needs UI feature to function properly.
The current solution i can think of is,
to un-install the UI feature,
1. un-install the composite feature first
2. install the other features that remained in the
composite feature programatically (In this case Server feature).
I can do this by using some feature tagging as stated in the equinox book.
Is this the proper way to do this ?.
Is there a better way provided by the P2 provisioning framework?
Is there anything wrong with my composite feature approach. (I follow
composite feature approach, so i can give one feature to the end user
rather than providing 2,3 features. )
Your feedback is much appreciated.