The service.id and objectClass properties must be set by the *framework* so they will always be returned in whatever case the framework uses internally. That ought to be the same as the value of the SERVICE_ID and OBJECTCLASS constants, but there's no guarantee.
All other properties need to follow the "same case as it was last set" rule, even if they are standard properties defined by OSGi. As for *why* that rule is there you'd have to ask BJ or Peter. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ikuo Yamasaki Sent: June 20, 2006 2:29 PM To: osgi-dev@bundles.osgi.org Subject: [osgi-dev] case of ServicePropety keys Hi, # I'm not sure if my questions should be posted on dev ml. The spec (r4.core.pdf) says "A Framework must return the key in ServiceReference.getPropertyKeys in exactly the same case as it was last set." I have questions on it. In advance, imagin that a Dictionary object with a key of "Service.Id" and a value for it is specified at its service registration. According the spec, framework must keep not the value specified but one that framework sets for this key. As far as I understand, ServiceReference.getPropertyKeys must return not Constants.SERVICE_ID="service.id" but "Service.Id". # The same thing can be said about OBJECTCLASS. Q1. Is my understanding correct ? Q2. Why did OSGi Alliance decide the spec as "A Framework must return the key in ServiceReference.getPropertyKeys in exactly the same case as it was last set." ? (why not decided as "return keys in lower case", at least for Constants.*** keys) --------------------- NTT Cyber Solutions Laboratories Ikuo YAMASAKI E-mail: [EMAIL PROTECTED] _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
