On Sep 14, 2007, at 23:36 , Rodrigo Madera wrote:
Are you sure you can't manage to write a book?
At the moment, quite sure ;)
Well, at least help me understand this OSGi jargon a little bit more:
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,
including
any
permitted headers; they must not have their own class loader.
Fragments
must have their own Protection Domain.
Can you please clarify the portions in red?
1) Host Bundle. WT* is it?
The host bundle is the bundle you attach the fragment bundle to. For
example, let's say you have a bundle that contains a Swing UI, and
for this UI you want to provide several translations. The UI itself
will be the "host bundle" and every language can be packaged as a
"fragment bundle". You can attach zero or more fragments to this host.
2) Before the host is resolved? What do you mean?
Bundles have a life cycle. They first get installed, then resolved,
starting, active, etc. In the example above, the host bundle and all
fragments are effectively "merged into one bundle" and then that
resulting bundle is resolved. Resolving means that all import package
statements are evaluated and wired up. A bundle can only be resolved
if all imports are actually available.
3) Part of the host... but what is a host in the first place?!?
as mentioned above... :)
Thanks for saving me some hair, if possible,
lol :)
Greetings, Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
