"Richard S. Hall" <[EMAIL PROTECTED]> writes: >> You can give the bundle any arbitrary location you want and use >> installBundle(String, InputStream)...this is what the OBR impl does, >> since it doesn't want the location is actually meaningless. > > That doesn't make sense..."since the location is actually meaningless"...
But based upon the interface contract of installBundle() as described by Mr. Hargrave, the location string is perhaps meaningless but must remain strongly correlated to a particular symbolic-name/version pair. He said that trying to install a bundle whose symbolic name and version match an already installed bundle must fail if the location string differs from the one used by the previously installed bundle. Does this location string match requirement not apply to the installBundle(String, InputStream) overload? >> What you need is to check to see if the symbolic name + version is >> already installed. Right, but what if I don't know the symbolic name and version of the candidate bundle? It sounds like I'd have to parse the MANIFEST.MF file myself first to get the candidate bundle's symbolic name and version. -- Steven E. Harris
