Community
Participate
Working Groups
In BundleIdBasedRegion.installBundle methods the region name is prepended to the passed in location string. This seems unnecessary and forces a transformed location onto the caller with a built in policy to include the region name in the location string. On one hand this seems like a good thing because it helps create unique location strings for cases where the same bundle is installed in multiple regions. On the other hand it forces a location string format on to the caller. I don't have a great suggestion for how to do something different here. Simply opening this bug to discuss. The javadoc currently does state that the region name is prepended to the given location. At a minimum the javadoc should state the format of the prepended region name (e.g. a '@' char is used to separate the region name from the location).
Why would any bundle care about the location used to install it? Is there some usage pattern I'm missing?
(In reply to comment #1) > Why would any bundle care about the location used to install it? Is there some > usage pattern I'm missing? Well, the current configuration admin spec is dependent on the bundle location used to install a bundle, if we change that under the covers it may surprise some provisioning agents that also configure using configuration Admin.
Closing as wontfix for now. I think the benefits of ensuring unique locations are important and what we do is fine for now.
Fine. Note that another method of making the location unique across regions was discussed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=346127#c8, but this would still presumably impact Config Admin uses cases as mentioned in Comment 2.
