Venkat, I understand your concern about adding other runtime-specific information into SCA. But since we would like to allow OSGi bundles used in SCA using < implementation.osgi/> to be also deployed outside of SCA in an OSGi runtime, we have to provide an OSGi bundle containing the SCA annotation APIs. This would just end up being a copy of sca-api.jar with the additional bundle manifest entries. Personally, I would prefer to have a single API jar file which can be used in all the Java-based runtimes supported by SCA if possible. But if contaminating SCA with OSGi-specific information is a concern, providing a separate jar may be the solution.
Thank you... Regards, Rajini On 7/6/07, Venkata Krishnan <[EMAIL PROTECTED]> 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 ;-). 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. 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. 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 >
