Sorry I meant to respond to you earlier, but keep getting bogged down with our current release. I know we have made some clarifications to fragment attachment since the R4.1 specification was released. We will have to go through the latest spec to ensure this is made clear. Thanks for opening a bug.
Tom
From: Alan Cabrera <[EMAIL PROTECTED]>
To: OSGi Developer Mail List <[email protected]>
Date: 06/10/2008 02:37 PM
Subject: Re: [osgi-dev] Attaching fragments
On Jun 8, 2008, at 5:49 PM, Alan Cabrera wrote:
On Jun 8, 2008, at 4:10 PM, Thomas Watson wrote:>
> What happens when a fragment has an import to a package that
the
> resolve bundle space cannot provide?
The fragment will not resolve and will not attach to a host
bundle.
This should not prevent any possible matching host bundles from
resolving if their individual constraints can be resolved.
>
> What happens when an export becomes available for that
fragment?
Then the fragment may be allowed to resolve and attach to a
host
bundle, but this cannot be done dynamically to an already
resolved
host. A fragment bundle cannot attach and add static
constraints
to and already resolved host bundle. Fragment bundles that
have
additional constraints which the host does not have can only
be resolved and attach to a host bundle at the same time as the
host bundle is being resolved.
Understood. I'm not sure where this is stated in the spec. Is this
handled by the clause:
"Append the import definitions for the Fragment bundle that do not
conflict
with an import definition of the host to the import definitions of
the
host bundle."
If so then that strikes me as a vague statement in the spec as I took
it to mean imports that have the same constraints not new imports.
If this is not where the spec dictates the above behavior, then I
missed something.
I assume that since on one has replied that this is obtained by looking at
the RI. I'll file something w/ OSGi to update the spec.
Regards,
Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
