On Mar 15, 2010, at 9:09 , Felix Meschberger wrote: > I have an incertainty about Service PID syntax as well as enforcement of > it in the ConfigurationAdmin service. > > As specified in Section 5.2.6, Persistent Identifier (PID), a PID is > defined the same as a symbolic-name as defined in Section 1.3.2, General > Syntax Definitions (all in the R 4.2 Core Spec). Such PIDs are referred > to in the Configuration Admin specification to identify configurations. > > My questions: > > (1) One of the examples in Section 104.3.1.3, Devices, of the > Compendium spec seems to violate this restriction proposing > the string "802-00:60:97:00:9A:56" as a PID (this is invalid > because colons are not allowed in symbolic names). > Is this a bug or intention ?
Both 5.2.6 and 104.3.1 mention that a PID *SHOULD* (not MUST) follow the symbolic-name syntax. > (2) The ConfigurationAdmin interface does not define an exception > to be thrown (e.g. IllegalArgumentException) if a PID argument > to the getConfiguration or createFactoryConfiguration methods > is invalid according to the definition of PID. > What should a ConfigurationAdmin implementation do ? > > As for the Apache Felix implementation: We currently do not check PID > values and accept any string. I would say, as 6.1.13.76 suggests: accept any value of the property that is a String, String[] or Collection of String. Greetings, Marcel _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
