I tend to agree, however :) right now this is really a problem for
users as configurations get not bound to a new installed bundle if a
previous version has been uninstalled.
What about FELIX-3360, if Julian is right we have a solution anyway :)

Regards
Carsten

2012/6/16 Felix Meschberger <[email protected]>:
> Hi
>
> Handling the bundle location of a configuration is IMHO outside of the scope 
> of Sling's OSGi Installer Configuration Factory.
>
> As such I don't think this is a good idea.
>
> Regards
> Felix
>
> Am 14.06.2012 um 09:04 schrieb Julian Sedding:
>
>> Hi Carsten
>>
>> I believe that this issue addresses the same symptom that I intended to
>> have addressed by FELIX-3360[0]. In case my interpretation of the OSGi Spec
>> is correct (tbd), your suggested fix would be a workaround for a Felix bug.
>>
>> Otherwise (i.e. if I read the spec wrongly), I support your fix, as I
>> believe that would be the expected behavior.
>>
>> Regards
>> Julian
>>
>> [0] https://issues.apache.org/jira/browse/FELIX-3360
>>
>>
>> On Thursday, June 14, 2012, Carsten Ziegeler (JIRA) wrote:
>>
>>> Carsten Ziegeler created SLING-2510:
>>> ---------------------------------------
>>>
>>>            Summary: Reset bundle location of a configuration if a bundle
>>> is uninstalled
>>>                Key: SLING-2510
>>>                URL: https://issues.apache.org/jira/browse/SLING-2510
>>>            Project: Sling
>>>         Issue Type: Improvement
>>>         Components: Installer
>>>   Affects Versions: Installer Configuration Factory 1.0.8
>>>           Reporter: Carsten Ziegeler
>>>
>>>
>>> If a bundle is uninstalled, the bundle location of a configuration still
>>> points to this bundle.
>>> If now a new version is installed, the configuration is not bound to the
>>> new bundle as this new bundle has a different bundle location.
>>>
>>> We could simply reset the bundle location of such configurations once a
>>> bundle is uninstalled
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> If you think it was sent incorrectly, please contact your JIRA
>>> administrators:
>>> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>>>
>



-- 
Carsten Ziegeler
[email protected]

Reply via email to