[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [equinox-dev] WiringAdmin vs PlatformAdmin
|
There is no WiringAdmin service. There is a org.osg.framework.wiring package that provides types that give access to the wiring of bundles installed into the framework. This is more a replacement to osgi service PackageAdmin than the Equinox specific PlatformAdmin.
That being said it looks like you could use the wiring package to help implement the functionality provided by StateResolverUtils. The StateResolverUtils seems to be used to determine what additional bundles may need to be refreshed in order to allow a fragment, with additional constraints, to resolve or for optional dependencies to be wired which were not in a previous resolution. The wiring package gives you access to the requirement and capabilities declared by the bundles. You could likely rebase StateResolveUtils on the wiring package to determine this by introspecting the requirements of unresolved fragments and optional requirements of resolved bundles.
Tom
Pascal Rapicault ---06/19/2011 01:48:09 PM---With the introduction of the WiringAdmin service, could someone shed some light on its relationship with equinox owns PlatformA
From: |
Pascal Rapicault <pascal@xxxxxxxxxxxx> |
To: |
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
Date: |
06/19/2011 01:48 PM |
Subject: |
[equinox-dev] WiringAdmin vs PlatformAdmin |
With the introduction of the WiringAdmin service, could someone shed some light on its relationship with equinox owns PlatformAdmin and especially the State aspect of that one.
The reason I'm asking is that simpleconfigurator has dependencies on PlatformAdmin (see class StateResolverUtils) and I would like to know if it would make sense to change this to use WiringAdmin instead.
Thx
PaScaL
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev