Richard S. Hall wrote:
Sahoo wrote:
As per the R4 spec section 3.14, a fragment bundle does not have its
own class loader. I infer that there is no point in specifying a
fragment bundle in the Require-Bundle header. Question is what
happens if a bundle specifies a fragment bundle in Require-Bundle
manifest? Does the framework ignore this or complain? I don't
recollect to have read one way or the other in the spec. Should the
spec clarify this?
The spec specifically says in 3.13.1 that fragment and extension
bundles cannot be required, but you are correct in that I did not
readily see what to do when this happens.
After some discussion with Tom Watson, I guess the appropriate action is
simply fail to resolve the bundle. Essentially, the require-bundle
constraint would not have any valid candidates to resolve its
dependency, so the resolve would fail. This would be similar to the
normal case of a resolve failure where a candidate was not available at
all or its attributes (e.g., version) did not match.
-> richard
-> richard
Thanks,
Sahoo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
