You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Andy Piper <an...@bea.com> on 2006/12/18 16:20:40 UTC

RE: OSGi Binding

[Sorry for the very late comments, only just catching up]

I agree that fragments are a logical way to go here.

At 14:44 09/11/2006, Hawkins, Joel wrote:
>OSGi has a concept known as a Bundle Fragment. A fragment is packaged as
>a separate bundle, but at runtime acts is if it were packaged directly
>as part of the host bundle. My thought was to package runtime extensions
>as fragments, and designate the sca kernel bundle as the bundle host.
>Add to that a mechanism to populate the system composite tree with the
>extensions, and you've got something that (to me) sounds very much like
>what you've described above. Application bundles could specify a
>dependency on the sca kernel bundle, at inherit classloader access to
>all the extensions as a result.

andy 

_______________________________________________________________________
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.

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org