You can say that services have as an implicit version number which is the version number of the package providing the interface/class being implemented. That said, you have to be careful with the OBR section of the specification as what has been published is a *very* old version of the specification and OBR is likely to go under large change in the near future.
PaScaL
From: Saul Goode <[email protected]>
To: OSGi Developer Mail List <[email protected]>
Date: 09/18/2009 05:00 AM
Subject: [osgi-dev] Bundle Repository - service capability
RFC 112 (Bundle Repository) defines a service capability, which is very
helpful for automated management of service dependencies. But where does
this version number in the example come from? (see page 27 in PDF [1])
AFAIK services don't have any version numbers. Or do they? Is this
version just reserved for future use?
Thanks,
Saul
[1]: http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
