Re: [equinox-dev] Two bundles contributing to one package?

["Jeremy Volkman" <jvolkman@xxxxxxxxx>]

John,

Perhaps you're looking for Fragment Bundles?  From the Core spec:

Fragments are bundles that are attached to a host bundle by the Framework.
Attaching is done as part of resolving: the Framework appends the relevant
definitions of the fragment bundles to the host's definitions before the host
is resolved. Fragments are therefore treated as part of the host; they must not
have their own class loader.

In your case, it seems that B would be a fragment of A.

Also, you might look at Require-Bundle and the case of a split
package, which is defined as "a package which does not have a single
provider, but the contents can come from different bundles."

Jeremy



On 4/6/06, John Wells <jwells@xxxxxxx> wrote:
> Can I have two bundles which contribute to a single package?
>
> In other words, can I have:
>
> 1.  A bundle A that exports package com.foo with class A
> 2.  A bundle B that exports package com.foo with class B
> 3.  Have a bundle C that imports com.foo and gets access to both A and B
>
> ?
>
> It doesn't seem like I can do this...
>
> I've tried the following:
>
> In BundleA I had the following:
>
> Export-Package: com.foo;name=A
>
> In BundleB I had the following:
>
> Import-Package: com.foo;name=A
> Export-Package: com.foo;name=B
>
> In BundleC I have the following:
>
> Import-Package: com.foo;name=B
>
> Bundle C does not resolve!?!
>
> John Wells (Aziz)
> jwells@bea.comNOSPAM
> _______________________________________________________________________
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>