Hlavní menu
Nástroje |
OSGiBundleCompatibilityChecking.HomePage HistoryHide minor edits - Show changes to markup 10 March 2009, 17:13
by
- Added lines 7-16:
How to obtain package and service bindingsAvailable interfaces and services in OSGi are
28 February 2009, 15:53
by
- Changed lines 21-23 from:
Version spec and matching: For capabilities, one of their property types is "version". For requirements, LDAP filters are used (example in section 5.5.7 of the OBR RFC shows it, sec 5.6.3 mandates filter syntax to be enhanced by version ranges). The OSGi suggested scheme is to be used. to:
Version spec and matching:
28 February 2009, 15:48
by
- Changed lines 21-23 from:
Version spec and matching: For capabilities, one of their property types is "version". For requirements, LDAP filters are used (example in section 5.5.7 of the OBR RFC shows it). The OSGi suggested scheme is to be used. to:
Version spec and matching: For capabilities, one of their property types is "version". For requirements, LDAP filters are used (example in section 5.5.7 of the OBR RFC shows it, sec 5.6.3 mandates filter syntax to be enhanced by version ranges). The OSGi suggested scheme is to be used. 28 February 2009, 15:45
by
- Added line 13:
Changed lines 17-21 from:
Bundle Repository (OBR)In OBR terminology, the exported features are called "capabilities" (and imported ones "requirements") to:
Bundle Repository (OBR) -- http://www.osgi.org/Repository/HomePageExported features are called "capabilities". Imported ones ("requirements") are actually named filter expressions. Version spec and matching: For capabilities, one of their property types is "version". For requirements, LDAP filters are used (example in section 5.5.7 of the OBR RFC shows it). The OSGi suggested scheme is to be used. 28 February 2009, 15:30
by
- Changed lines 16-20 from:
to:
Bundle Repository (OBR)In OBR terminology, the exported features are called "capabilities" (and imported ones "requirements") 28 February 2009, 15:24
by
- Changed lines 13-19 from:
it would use string comparison.
interface="f.q.name" target="(creation.method=shallow-copy)"> the filter is manifested in the enclosing component as property (112.3.4) to:
28 February 2009, 15:23
by
- Changed lines 12-13 from:
sec 112.3.4 Selecting target svc is constrained by svc name and props, but exported services do not declare versions as first-class citizens (cf 112.4.6) so only the general mechanism of properties can be used (but these are on component, not service, level). Since the properties use LDAP syntax which allows wildcards, $\leq$ and $\geq$ operators, it should be possible to specify version range matching with the limitation that to:
Use of properties for version specification and matching:
Changed lines 15-16 from:
to:
interface="f.q.name" target="(creation.method=shallow-copy)"> the filter is manifested in the enclosing component as property (112.3.4) Deleted lines 27-33:
Explanation of R4 section 112.6 item 3: the rather complicated language says (if I understand correctly) that the 28 February 2009, 15:22
by
- Added lines 5-6:
Mostly with respect to compatibility evaluation, type matching. Changed lines 10-11 from:
to:
sec 112.3.4 Selecting target svc is constrained by svc name and props, but exported services do not declare versions as first-class citizens (cf 112.4.6) so only the general mechanism of properties can be used (but these are on component, not service, level). Since the properties use LDAP syntax which allows wildcards, $\leq$ and $\geq$ operators, it should be possible to specify version range matching with the limitation that it would use string comparison. 28 February 2009, 15:20
by
- Added lines 18-24:
Explanation of R4 section 112.6 item 3: the rather complicated language says (if I understand correctly) that the 28 February 2009, 15:05
by
- Changed lines 12-13 from:
OSGi filters use LDAP filter syntax (RFC 4515) and matching rules (RFC 4517) to:
OSGi filters use LDAP filter syntax (RFC 4515) and matching rules (RFC 4517, partially explained in OpenDS wiki) 28 February 2009, 14:52
by
- Changed lines 12-13 from:
OSGi filters use LDAP filter syntax (RFC 4515) to:
OSGi filters use LDAP filter syntax (RFC 4515) and matching rules (RFC 4517) 28 February 2009, 14:43
by
- Changed lines 10-15 from:
to:
28 February 2009, 12:14
by
- Changed line 7 from:
to:
28 February 2009, 12:05
by
- Changed lines 8-10 from:
to:
28 February 2009, 12:02
by
- Added lines 3-10:
Co víme o součástech OSGiDeclarative Services Specification (SCR, after Service Component Runtime)
Aside: SCR uses ``event strategy'' for binding services which is in fact dependency injection - the component declares setter and unsetter methods to bind and unbind a reference, these are called by the SCR ie the framework 28 February 2009, 12:01
by
- založení stránkyAdded lines 1-4:
OSGi Bundle Compatibility Checking - projekt na verifikaci typové kompatibility OSGi komponent a jejich vazeb. Viz oficiální stránky na skupině DSS. Patří do KategorieProjekty. |