public class FrameworkWiringImpl extends java.lang.Object implements FrameworkWiring
Modifier and Type | Method and Description |
---|---|
Bundle |
getBundle()
Returns the
Bundle object associated with this
BundleReference . |
java.util.Collection<Bundle> |
getDependencyClosure(java.util.Collection<Bundle> bundles)
Returns the dependency closure for the specified bundles.
|
java.util.Collection<Bundle> |
getRemovalPendingBundles()
Returns the bundles that have
non-current , in use bundle wirings. |
void |
refreshBundles(java.util.Collection<Bundle> bundles,
FrameworkListener... listeners)
Refreshes the specified bundles.
|
boolean |
resolveBundles(java.util.Collection<Bundle> bundles)
Resolves the specified bundles.
|
public Bundle getBundle()
BundleReference
Bundle
object associated with this
BundleReference
.getBundle
in interface BundleReference
Bundle
object associated with this
BundleReference
.public void refreshBundles(java.util.Collection<Bundle> bundles, FrameworkListener... listeners)
FrameworkWiring
The technique by which the framework refreshes bundles may vary among different framework implementations. A permissible implementation is to stop and restart the framework.
This method returns to the caller immediately and then performs the following steps on a separate thread:
dependency
closure
of the specified bundles. If no bundles are specified, compute
the dependency closure of the removal
pending
bundles.
ACTIVE
state will be stopped as described in the Bundle.stop
method.
RESOLVED
state is unresolved and thus moved to the INSTALLED
state. The
effect of this step is that bundles in the dependency closure are no
longer RESOLVED
.
UNINSTALLED
state is removed from the dependency closure and is
now completely removed from the Framework.
ACTIVE
state prior to Step 2 is started as described in the Bundle.start
method, causing all bundles required for the restart to be resolved. It
is possible that, as a result of the previous steps, packages that were
previously exported no longer are. Therefore, some bundles may be
unresolvable until bundles satisfying the dependencies have been
installed in the Framework.
For any exceptions that are thrown during any of these steps, a framework
event of type FrameworkEvent.ERROR
is fired containing the
exception. The source bundle for these events should be the specific
bundle to which the exception is related. If no specific bundle can be
associated with the exception then the System Bundle must be used as the
source bundle for the event. All framework events fired by this method
are also delivered to the specified FrameworkListener
s in the
order they are specified.
When this process completes after the bundles are refreshed, the
Framework will fire a Framework event of type
FrameworkEvent.PACKAGES_REFRESHED
to announce it has completed
the bundle refresh. The specified FrameworkListener
s are notified
in the order specified. Each specified FrameworkListener
will be
called with a Framework event of type
FrameworkEvent.PACKAGES_REFRESHED
.
refreshBundles
in interface FrameworkWiring
bundles
- The bundles to be refreshed, or null
to refresh
the removal pending
bundles.listeners
- Zero or more listeners to be notified when the bundle
refresh has been completed. The specified listeners do not need to
be otherwise registered with the framework. If a specified
listener is already registered with the framework, it will be
notified twice.public boolean resolveBundles(java.util.Collection<Bundle> bundles)
FrameworkWiring
If no bundles are specified, then the Framework will attempt to resolve all unresolved bundles. This method must not cause any bundle to be refreshed, stopped, or started. This method will not return until the operation has completed.
resolveBundles
in interface FrameworkWiring
bundles
- The bundles to resolve or null
to resolve all
unresolved bundles installed in the Framework.true
if all specified bundles are resolved; false
otherwise.public java.util.Collection<Bundle> getRemovalPendingBundles()
FrameworkWiring
non-current
, in use
bundle wirings. This
is typically the bundles which have been updated or uninstalled since the
last call to FrameworkWiring.refreshBundles(Collection, FrameworkListener...)
.getRemovalPendingBundles
in interface FrameworkWiring
Bundle
s which
have non-current, in use BundleWiring
s, or an empty
collection if there are no such bundles.public java.util.Collection<Bundle> getDependencyClosure(java.util.Collection<Bundle> bundles)
FrameworkWiring
A graph of bundles is computed starting with the specified bundles. The
graph is expanded by adding any bundle that is either wired to a package
that is currently exported by a bundle in the graph or requires a bundle
in the graph. The graph is fully constructed when there is no bundle
outside the graph that is wired to a bundle in the graph. The graph may
contain UNINSTALLED
bundles that are
removal pending
.
getDependencyClosure
in interface FrameworkWiring
bundles
- The initial bundles for which to generate the dependency
closure.