Hi, I wanted to give official feedback that my customers are surprised that OSGi service API is based on obsolete data types.
From the Javadoc of Dictionary: ---- NOTE: This class is obsolete. ---- This makes the OSGi service API look outdated for several of the customers I discussed this. OSGi ds hides this a bit but sometimes the low-level API must be used. So for those involved in the OSGi spec, maybe you can consider deprecating the old methods in BundleContext and providing new ones with non-obsolete API, e.g., Map? I'm aware that this is "just a mailing list" but AFAIK several of the subscribed people here are involved in the OSGi specification. Best regards, Lars -- Eclipse Platform project co-lead CEO vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
