Yes I am planning deploy equinox jars into Felix, because Felix has developed the OBR repository that I want to use. As well, I going to check if this repository can be deployed into Equinox. Thanks, Santiago
2009/7/17 Raymond Feng <[email protected]> > First of all, I just removed the dependency on "org.eclipse.core.adaptor" > by using the org.osgi.framework.launch API introduced in Equinox 3.5 (as > well as Felix 1.8.0). > > Back to the original issue, do you plan to deploy the equinox jars into > Felix as well? If not, then the optional import to org.eclipse.core.adaptor > won't be harmful as it is only used by the test case which is not packaged > in the bundle. Am I missing anything? > > Thanks, > Raymond > > *From:* Santiago Miguel Aranda Rojas <[email protected]> > *Sent:* Friday, July 17, 2009 4:58 AM > *To:* [email protected] > *Subject:* Re: Deploy Tuscany distribution from OBR Repository > > With regards to tuscany-extensibility-equinox dependency on > org.eclipse.core.adaptor, there is a problem with the fact that the bundle > also imports org.osgi.framework, and this is provided also by the same > bundle that provides org.eclipse.core.adaptor. > Taking into account that Felix framework also provides org.osgi.framework. > When using OBR there could be a conflict among the system bundle currently > in operation (Felix) and the deployable ones that has a dependency to > Equinox framework (package org.eclipse.core.adaptor). So when the dependency > tree is built, a conflict appears (in the case that org.osgi.framework has > the same version in Felix and Equinox). > > Has you considered this scenario? I think it represents a potential > conflict in order to the portabiltiy of Tuscany in different OSGi framework. > > If you have any question or suggestion I would try to explain it in another > way. > > 2009/7/16 Raymond Feng <[email protected]> > >> At this moment, the OSGi integration with Tuscany 2.x has only been >> tested with Equinox. It shouldn't be too difficult to bring them up with >> Felix. If you would like to try, I would be happy to help you whenever you >> run into issues. >> >> The key difference between Felix and Equinox is the how the frameworks are >> bootstrapped. We can simply add a module such as node-launcher-osgi-felix to >> cover that. I'm also considering to use the latest framework launch APIs to >> unify both. >> >> tuscany-extensibility-equinox has an option dependency on >> org.eclipse.core.runtime.adaptor for JUNIT testing. It should be fine for >> Felix. >> >> I suggest that you start with the bundles in the distribution. Most of >> them should be agnostic to the OSGi runtime. >> >> The OBR idea is interesting. Equinox also has the p2 infrastructure. It >> seems that additional metadata are needed to help the repo manage the >> Tuscany bundles. >> >> Thanks, >> Raymond >> >> *From:* Santiago Miguel Aranda Rojas <[email protected]> >> *Sent:* Thursday, July 16, 2009 3:04 AM >> *To:* [email protected] >> *Subject:* Re: Deploy Tuscany distribution from OBR Repository >> >> We are considering to deploy Tuscany over Felix 1.8.0 OSGi framework. >> Because they have developed the OBR repository. We have found a strong >> dependency in some Tuscany bundles with Equinox OSGi framework. For instance >> tuscany-extensibility-equinox-2.0-M3.jar bundle has in its MANIFEST.MF an >> Import-Package clause that includes the package >> org.eclipse.core.runtime.adaptor. The same happens with bundles: >> tuscany-node-launcher-equinox-2.0-M3.jar and spring-core-2.5.5.jar. >> This implies in my opinion that Tuscany will only works fine if it is >> deployed in Equinox OSGi framework. Are you considering that Tuscany will be >> deployed over other OSGi framework implementations like Felix. >> >> >> >> >> >> 2009/7/15 Simon Laws <[email protected]> >> >>> Ok, and let us know if you need more info. It'll be really interesting >>> to hear how you get on. >>> >>> Simon >>> >> >> >
