On 1/3/11 14:02, Neil Bartlett wrote:
DS principally defines *components*. A component can depend on a
service by declaring a<reference> element in its XML descriptor (or
if you're using the cool Bnd annotations, an @Reference annotation in
the Java source).
In addition a component can itself provide a service, using the
<service> element with one or more nested<provide> elements.
Put these together and you have your so-called "service to service"
dependencies.
Not quite, see my reply.
-> richard
Regards,
Neil
On Mon, Jan 3, 2011 at 6:54 PM, Michael Köndling<[email protected]> wrote:
H. Cervantes and R.S. Hall write in Beanome: A Component Model for the OSGi
Framework<http://www.humbertocervantes.net/papers/VIVIAN2002.pdf> that
there are three types of dependencies in OSGi:
Bundle-to-package
Bundle-to-service
Service-to-service
I understand that the article was written in 2002 (prior to DS).
Bundle-to-package dependencies can (or have to) be expressed with
Import-Package. Bundle-to-service dependencies can also be expressed through
service components with DS.
But what about Service-to-service dependencies. Would it be correct to say
that they are also covered by DS?
Greetings,
Michael
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
