Hi Joel and Jim, I'm trying to find out what's the best way for us to create for the SCA extensions (packaged as JAR) the required OSGi bundles.
Currently I see two possibilities: 1) Maven-OSGi-Plugin The Maven OSGi Plugin (under development at the Apache Felix project) allows you to generate OSGi bundles out of standard JARs. You have to configure the path to the manifest (which could be a standard java manifest). Additonal headers like Bundle-ClassPath, Export/Import-Package, Bundle-Activator can be defined. Configuration happens in the pom.xml file. >From my point of view we could use it for the OSGi container. The only 'problem' is that the values in the pom.xml have to be hardcoded, we cannot get them easily out of the scdl file. Further information can be found here: http://cwiki.apache.org/FELIX/osgi-plugin-for-maven-2.html 2) Creation of virtual bundles One other possibility which might fit for Tuscany is to generate virtual bundles on the fly out of the JARs. The OSGi-Spring integration provides this virtual bundle functionality, see: http://www.springframework.org/osgi/specification I had a look to the Source Code. The spring-osgi-core bundle provides a class VirtualBundleFactoryBean which allows you to create a bundle. It provides methods to set the version, the artifactId, groupId, exports, imports etc. The bundle does only exist in the RAM, not on the disc, it's virtual. I could imagine having something like an Extension-Directory-Listener-Bundle which read the configured information out of the scdl files in the extension JARs and creates via the VirtualBundleFactoryBean for every extension a bundle. Does every extension bundle require its own bundle context? I'm asking because this might be difficult to achieve with this approach. What do you think, can we use one of the proposed possibilities? Thanks Nicole --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
