[Configurator] Difference between R7 Java API and Spec
bjhargrave opened this issue · 6 comments
Original bug ID: BZ#3076
From: @cziegeler
Reported version: R7
Comment author: @cziegeler
Unfortunately we have a difference between the released configurator 1.0 API and the released spec text.
While the spec states Table 150.1 at https://osgi.org/specification/osgi.cmpn/7.0.0/service.configurator.html#d0e131566 the property to be named "symbolicname" the static field PROPERTY_SYMBOLIC_NAME in ConfiguratorConstants (https://osgi.org/specification/osgi.cmpn/7.0.0/service.configurator.html#org.osgi.service.configurator.ConfiguratorConstants) specifies this as "symbolic-name" (notice the extra dash)
The reference implementation is using this constant, therefore checking for a property name using the dash.
I think we need to change one or the other, changing the spec text is probably the easier solution.
Comment author: @bjhargrave
Yes, sounds like we need to fix the spec text for R8 and issue an errata for R7.
https://osgi.org/specification/osgi.cmpn/7.0.0/service.configurator.html#org.osgi.service.configurator.ConfiguratorConstants.PROPERTY_SYMBOLIC_NAME is the proper name: ":configurator:symbolic-name"
Comment author: @cziegeler
@ BJ What needs to be done to get the errata?
Comment author: @bjhargrave
Fixed for R8 by https://osgi.org/gitweb/build.git/commit/914a00e3f1b2b487a9d135cf4fbc2fdb16e706ad
Errata text:
150.3.1:
Table 150.1 is updated to correct the spelling of ':configurator:symbolic-name'. It incorrectly stated the spelling as ':configurator:symbolicname'.
150.11:
The discussion of the osgi.identity capability is updated to correct the spelling of ':configurator:symbolic-name'. It incorrectly stated the spelling as ':configurator:symbolicname'.
Comment author: @bjhargrave
I also corrected the html spec published on the osgi.org site.
Comment author: @bjhargrave
This is fixed in HEAD and will be picked up in the next release of the configurator spec (Enterprise R7 and Compendium R8).
Request to publish errata on www.osgi.org has been made to Mike Francis (www.osgi.org editor).