Andy,

I've got a prototype (minus the virtual bundle bit that Nicole is
looking at) out at http://people.apache.org/~jhawkins/Tuscany/. I'd be
interested in your thoughts on the implementation. I'm been off working
on other things lately, but I'm trying to get back to it. :-)

Thanks,
Joel

-----Original Message-----
From: Andy Piper [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 18, 2006 10:21 AM
To: tuscany-dev@ws.apache.org
Cc: tuscany-dev@ws.apache.org
Subject: 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it. 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to