Hi, I second the proposal of adding OSGi metadata to the jars.
Some months ago we had a similar discussion on this list, there we said, that we should not generate OSGi Bundles at build time, but generate OSGi bundles out of the JAR files on the fly. We tried this out (it's easy for simple bundles/Jars), but for bundles that require other bundles it's difficult. We do not have enough information for the mapping to OSGi in the scdl files (e.g. should we use required bundle, import etc. ?) Currently we are talking only about the sca-api.jar, but the next question will be about other jars like axis, which should be used in the OSGi container as well. To keep it simple it would propose to generate the required bundles already at build time. Best regards Nicole -----Ursprüngliche Nachricht----- Von: Mike Edwards [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 6. Juli 2007 14:45 An: [email protected] Betreff: Re: Make sca-api.jar an OSGi bundle Venkat, I'm in favour of adding OSGi metadata to relevant jars to enable them to act as OSGi bundles. I think that OSGi is in a different space than "other runtimes" and that supporting it is a good idea. Other comments inline... Yours, Mike Venkata Krishnan wrote: > Hi, > > This seems ok since you say it does not have side effects for other > consumers. However, I wonder if we can keep doing this for accomodating > other runtimes as well - am not sure what the others might want or if > they'd > need something not as simple as this - just postulating here ;-). OSGi is less "another runtime" and more "a whole class of runtimes", so in that sense it is special. OSGi is a framework for organizing runtimes into logical chunks. Many runtimes use OSGi - the most famous being Eclipse. I think that we should make it easy for Tuscany SCA (and SDO for that matter) to fit into a runtime that is using OSGi. To do that ideally requires us to add some OSGi metadata to relevant jar files. > Or, > seeing it from the other side I wonder if it would be ok to consider > specific inclusions in OSGi bundles to facilitate their handling in a SCA > runtime. This is looking at it the other way around. I believe that this is the work that Rajini and others are already doing in building an <implementation.osgi .../> for Tuscany, to allow stuff built using OSGi to work cleanly within Tuscany. > > So, from what I am able to comprehend, I'd prefer to avoid this tie in. > Maybe we should also hear what others have to say. It is no tie-in. Adding OSGi metadata does not make any of our JARs unusable by anyone else and it does not force the use of OSGi - and the handling of the OSGi metadata in the build process can be pretty simple, I believe. There is a whole separate question about whether we should consider building the whole Tuscany SCA runtime using OSGi. There are merits to that, but also potential downsides - however, we can have a completely separate debate about that some other time, since it has nothing to do with Rajini's current proposal. > > Thanks > > - Venkat > > On 7/6/07, Rajini Sivaram <[EMAIL PROTECTED]> wrote: >> >> Hello, >> >> Could we convert sca-api.jar to an OSGi bundle so that bundles used by >> the >> OSGi implementation type can import SCA annotations and interfaces? This >> may >> be already being addressed in the other OSGi related work, but the change >> is >> simple and will enable the support for SCA annotations in OSGi bundles to >> progress. >> >> Converting sca-api.jar to an OSGi bundle would just need the addition >> of a >> few entries in the manifest file for the jar, and will not affect any >> other >> modules using the jar file as a regular jar. >> >> Thank you... >> >> Regards, >> >> Rajini >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
