On 6/22/10 10:16, Justin Edelson wrote:
This is not, as far as I know, accurate.
org.osgi.framework.system.packages.extra exposes packages from the host
application to embedded bundles, not vice versa.
I think that is what he is trying to say by the reflection comment, if
not, then you are right...this is how you can expose stuff from the host
to the embedded bundles.
-> richard
Justin
On 6/22/10 2:21 AM, khepel lak wrote:
Just on remark about the org.osgi.framework.system.packages.extra: it is
handy when u have embedded felix and your host application is not a bundle
and but wants to use the bundles. If some classes (API) are
only available as bundle(s), u have to use reflection to use the bundles.
Correct me on this part if I am wrong.
On Tue, Jun 22, 2010 at 12:14 AM, Kelvin Chan
<[email protected]>wrote:
Will won't get to see anything except for what they specifically import.
This is true for packages coming from other bundles or the class path.
The exception to this rule is boot delegation. If you add packages to the
boot
delegation property. This gives bundles access to the specified packages
from the class path without the bundles having to import them at all.
This is
not a good thing and shouldn't be used in general.
Luckily, as Ali points out, you don't need the source to create a bundle,
you
just need to add the appropriate OSGi metadata to the JAR file's
manifest.
-> richard
Richard,
Thanks for the help and clarification. The road to OSGi mastery is, well,
brighter now.
:)
kel
NOTICE: This communication is intended only for the use of the person or
entity named above and may contain information that is confidential or
legally privileged. If you are not the intended recipient named above or a
person responsible for delivering messages or communication to the intended
recipient, you are hereby notified that any use, distribution, or copying of
this communication or any of the information contained in it is strictly
prohibited. If you have this communication in error, please notify me
immediately by telephone and then destroy or delete this communication, or
return it to me by mail if requested. Thank you for your attention and
cooperation.
---------------------------------------------------------------------
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]
