[ 
https://issues.apache.org/jira/browse/FELIX-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227505#comment-13227505
 ] 

Carsten Ziegeler edited comment on FELIX-3334 at 3/12/12 1:26 PM:
------------------------------------------------------------------

To be honest, i'm not using this implementation very intensively, so chances 
are that there are more concurrency issues.
I'm wondering if we need the support for different stores at all or just go 
with the default store and are done. So far I haven't heard that someone is 
using its own store implementation
                
      was (Author: cziegeler):
    To be honest, i'm not using this implementation very intensively, so 
changes are that there are more concurrency issues.
I'm wondering f we need the support for different stores at all or just go with 
the default store and are done. So far I haven't heard that someone is using 
its own store implementation
                  
> PreferencesManager can throw NPE after being stopped.
> -----------------------------------------------------
>
>                 Key: FELIX-3334
>                 URL: https://issues.apache.org/jira/browse/FELIX-3334
>             Project: Felix
>          Issue Type: Bug
>          Components: Preferences Service
>    Affects Versions: prefs-1.0.4
>            Reporter: J.W. Janssen
>            Assignee: Carsten Ziegeler
>              Labels: patch
>             Fix For: prefs-1.0.6
>
>         Attachments: felix-prefs-3334-2.patch, quickfix-new.patch
>
>
> PreferencesManager#bundleChanged tries to intercept bundles that are 
> uninstalled. However, if the PreferencesManager itself is stopped, it does 
> not unregister itself as bundle listener, causing possible NPEs when other 
> bundles depending on the preferences service are stopped later on, for 
> example during a shutdown.
> I've got a patch available, will attach it to this issue to be applied.

--
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

        

Reply via email to