On Apr 11, 2007, at 5:22 PM, Steven E. Harris wrote:
In recent discussion on the felix-dev list, BJ Hargrave wrote¹ of a
bundle's location string,
Think of location as a primary key for a Bundle.
If that's the case, then Bundle.update() seems like a strange
interface. It uses the current location string to fetch a new version
of the same bundle, or at least a bundle with the same symbolic name.
It doesn't have to be the same bundle or the same symbolic
name...there is no requirement on that. I could use update to
completely change the bundle to a different bundle.
But what if the location string -- interpreted as a URL -- resolves to
a bundle with the /same/ symbolic name and /same/ version? Does that
just replace the current bundle associated with that location string?
For update, you are just replacing the bundle that you are updating.
Or what if the location string resolves to a bundle with a /different/
symbolic name? Say that bundle {foo, 1.0.0} is installed with a
location string of "http://localhost/supplyRandomBundle.cgi";, and we
call Bundle.update(), and the resolved input stream provides bundle
{bar, 2.3.4}? Does the framework care?
No.
-> richard
Footnotes:
¹ http://www.mail-archive.com/[email protected]/
msg04866.html
--
Steven E. Harris
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
