This itest has been fixed now with TUSCANY-1569 so how about including implementation-osgi in the 0.99 release? It would add about 500K of Felix dependencies which doesn't seem a big deal, so i think we should include it.
...ant On 8/20/07, Rajini Sivaram <[EMAIL PROTECTED]> wrote: > > Ant, > > I will take a look at the intermittent test failure in itest/osgi > -implementation. > > > Thank you... > > Regards, > > Rajini > > On 8/16/07, ant elder <[EMAIL PROTECTED]> wrote: > > > > Hi SCA/OSGi-ers, > > > > Just bringing this up again to see if there is any interesting in moving > > this along still. We've been talking about having a Tuscany 1.0 release > > in a couple of months, be great if we could have a good OSGi story for that. > > Also the Apache Felix 1.0 release is out now and the existing > > implemention.osgi code has been moved off SNAPSHOTs to use Felix 1.0 so > > we can now include that in releases (though i think one of the itests still > > has an intermittent failure so would be good to fix that as well). > > > > ...ant > > > > > > On 6/29/07, Hawkins, Joel < [EMAIL PROTECTED]> wrote: > > > > > > Hi SCA/OSGi-ers. > > > > > > I did some initial work back during the M2 days (working with Nicole) > > > to > > > host Tuscany in an Equinox runtime. It looks like I may have some time > > > to re-engage during the next few months, so is there anything in > > > particular that I could be looking at to help move the OSGi efforts > > > ahead? Like Bill and Raymond below, my primary interest is in seeing > > > OSGi used as a container for hosting SCA. > > > > > > Cheers, > > > Joel > > > > > > -----Original Message----- > > > From: Rajini Sivaram [mailto: [EMAIL PROTECTED] > > > Sent: Wednesday, June 27, 2007 4:20 AM > > > To: tuscany-dev@ws.apache.org > > > Subject: Re: Contribute to SCA-OSGi integration > > > > > > Sebastien, > > > > > > Graham and I will be looking at the support for packaging of SCA > > > contributions as OSGi bundles, once the work on implementation.osgi is > > > complete. > > > > > > > > > Thank you... > > > > > > Regards, > > > > > > Rajini > > > > > > On 6/23/07, Jean-Sebastien Delfino <[EMAIL PROTECTED] > wrote: > > > > > > > > Bill Barnhill wrote: > > > > > Hi, > > > > > > > > > > As I may have mentioned earlier I also have been working on the > > > SCA-OSGi > > > > > integration, but from the third aspect that Raymond mentions, > > > using > > > > > OSGi as > > > > > an underlying technology for an SCA container providing an > > > extension > > > > > mechanism, dependency resolution and service registry > > > capabilities. > > > > > > > > > > I think my work would dovetail nicely with the work Rajini and > > > Graham > > > > > have > > > > > been doing. Would it be possible to create an osgi directory under > > > > > contrib > > > > > with a subdir under that for each of our efforts (host, binding, > > > > > implementation) > > > > > > > > > > What do you think? > > > > > > > > > > > > > Hi Bill, > > > > > > > > That sounds like a good idea. Tuscany modules are not that different > > > > from OSGI bundles, I think it wouldn't be too difficult to package > > > them > > > > as actual bundles, and come up with a variation of host-embedded > > > that > > > > will load them as such, allowing for some isolation and better > > > > jar/bundle dependency management. > > > > > > > > Do you have the structure you need with sca/modules/host-osgi? Do > > > you > > > > have code that we can look at? > > > > > > > > Any questions or issues that we can help with? > > > > > > > > On a different, but related subject, has anybody started on > > > supporting > > > > the package of (application) SCA contributions (as defined by the > > > SCA > > > > assembly spec) as OSGI bundles? > > > > > > > > Thanks > > > > > > > > -- > > > > Jean-Sebastien > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > > > >
