You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Thomas Watson (JIRA)" <tu...@ws.apache.org> on 2006/08/10 16:01:15 UTC

[jira] Commented: (TUSCANY-610) Initial OSGi support effort

    [ http://issues.apache.org/jira/browse/TUSCANY-610?page=comments#action_12427224 ] 
            
Thomas Watson commented on TUSCANY-610:
---------------------------------------

Joel,

Is there some more documentation on this work?  I do not know much about how SCA works but I would like to see how this fits into the OSGi environment.  Can you provide some steps to get this running on Equinox?  Any other information on how SCA and OSGi can interact with each other would also be interesting to me.

Thanks.  Tom.

P.S.  I'm a developer on the Equinox Framework team.  Please let us know if you need any assistence from the Equinox team to advance this work (bug fixes, enhancements, questions etc.).

> Initial OSGi support effort
> ---------------------------
>
>                 Key: TUSCANY-610
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-610
>             Project: Tuscany
>          Issue Type: New Feature
>         Environment: Equinox implementation of OSGi
>            Reporter: Joel Hawkins
>         Attachments: OSGI-SCA.zip
>
>
> An initial implementation of an OSGi binding for exposing SCA services as OSGi services.
> An initial implementation of an OSGi implementation for reusing OSGi services as SCA atomic components
> An OSGi-aware bootstrap environment (which can probably be reduced a bit)
> A repackaging of some of the SupplyChain example
> There's one class derived from an  EPL-copyrighted class - I left the EPL copyright intact. 
> The zip contains the samples, the OSGi binding, and a patch for the core. Most of the patch is the OSGi launcher code. I don't think it belongs in the core, but that's where I had it while developing. The only other bit in the patch is a change of two of the Defaultbootstrapper's fields from private to protected.
> Also, some of the OSGi packaging for existing jars (spi, commands, etc) aren't part of the zip. Not sure how you want to deal with the repackaging issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Re: [jira] Commented: (TUSCANY-610) Initial OSGi support effort

Posted by Jim Marino <jm...@myromatours.com>.
Hi Thomas,

I think we met at JavaOne briefly...I haven't had a chance to look  
closely at Joel's work yet (just waiting for the removal of the EPL  
licensed class) so I'll let him jump in with more details. I think  
one of the interesting areas is going to be with sharing services  
between the two environments. For example, being able to consume OSGi  
services from within SCA and having SCA able to export services to  
OSGi. Other frameworks like Spring are also building this type of  
bridge so OSGi will potentially allow us to access those as well.

Longer term, I think it would be interesting to see if OSGi and SCA  
services could potentially converge as they share a lot of things in  
common.

Thanks for the offer of help and as soon as Joel replaces the one  
class, we'll check in his patch so we can look at more specifics.

Jim


On Aug 10, 2006, at 7:01 AM, Thomas Watson (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/TUSCANY-610? 
> page=comments#action_12427224 ]
>
> Thomas Watson commented on TUSCANY-610:
> ---------------------------------------
>
> Joel,
>
> Is there some more documentation on this work?  I do not know much  
> about how SCA works but I would like to see how this fits into the  
> OSGi environment.  Can you provide some steps to get this running  
> on Equinox?  Any other information on how SCA and OSGi can interact  
> with each other would also be interesting to me.
>
> Thanks.  Tom.
>
> P.S.  I'm a developer on the Equinox Framework team.  Please let us  
> know if you need any assistence from the Equinox team to advance  
> this work (bug fixes, enhancements, questions etc.).
>
>> Initial OSGi support effort
>> ---------------------------
>>
>>                 Key: TUSCANY-610
>>                 URL: http://issues.apache.org/jira/browse/TUSCANY-610
>>             Project: Tuscany
>>          Issue Type: New Feature
>>         Environment: Equinox implementation of OSGi
>>            Reporter: Joel Hawkins
>>         Attachments: OSGI-SCA.zip
>>
>>
>> An initial implementation of an OSGi binding for exposing SCA  
>> services as OSGi services.
>> An initial implementation of an OSGi implementation for reusing  
>> OSGi services as SCA atomic components
>> An OSGi-aware bootstrap environment (which can probably be reduced  
>> a bit)
>> A repackaging of some of the SupplyChain example
>> There's one class derived from an  EPL-copyrighted class - I left  
>> the EPL copyright intact.
>> The zip contains the samples, the OSGi binding, and a patch for  
>> the core. Most of the patch is the OSGi launcher code. I don't  
>> think it belongs in the core, but that's where I had it while  
>> developing. The only other bit in the patch is a change of two of  
>> the Defaultbootstrapper's fields from private to protected.
>> Also, some of the OSGi packaging for existing jars (spi, commands,  
>> etc) aren't part of the zip. Not sure how you want to deal with  
>> the repackaging issue.
>
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the  
> administrators: http://issues.apache.org/jira/secure/ 
> Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/ 
> software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>


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