Just to back up what Felix said with a specification reference, please see OSGi Compendium section 112.4.2 "Service Component Header", which states:
"A Service-Component manifest header specified in a fragment is ignored by SCR. However, XML doc- uments referenced by a bundle’s Service-Component manifest header may be contained in attached fragments." On Mon, Aug 19, 2013 at 1:10 PM, Felix Meschberger <[email protected]> wrote: > Hi > > Am 19.08.2013 um 14:01 schrieb Roland: > >> Hello OSGi-experts, >> It is possible to define a declarative Service in a fragmented bundle? > > Yes. But the host bundle must be open to this. By open, I mean the host > bundle must have the Service-Components header configured such that any > descriptors in the fragment will be found. For example: > > Service-Components: OSGI-INF/scr/*.xml > > will find all .xml files in the OSGi-INF/scr folder of the host bundle all > the attached fragments. > >> I >> just want to separate api and impl. > > You don't need fragments do separate API from implementation. In fact, > separation is a great thing: The API bundle just exports the API and > implementation bundle just imports (but does not export anything). > >> by adding a service-component to a >> fragmented bundle whereas the host exports its interface. > > No, the Service-Components header in fragments is ignored. > > Regards > Felix > >> >> Thanks an regards >> Roland >> >> >> >> -- >> View this message in context: >> http://apache-felix.18485.x6.nabble.com/DS-fragments-tp5004610.html >> Sent from the Apache Felix - Users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
