Re: NPE in ConfigAdmin

Hi Felix, On 26 Sep , 2008, at 17:03 , Felix Meschberger wrote: Hi Peter, Though I think, this is certainly a corner case, it is not a nice behaviour. The correct behaviour would probably be to check whether the bundle is still set on the service reference and abort processing if not. Y

Re: NPE in ConfigAdmin

Hi Peter, Though I think, this is certainly a corner case, it is not a nice behaviour. The correct behaviour would probably be to check whether the bundle is still set on the service reference and abort processing if not. Can you please file a JIRA issue to track this ? Thanks. Regards Felix pe

NPE in ConfigAdmin

Hi, I get a NullPointerException in the ConfigAdmin's update thread, that is originating from the following piece of code (ConfigurationManager): private class ManagedServiceFactoryUpdate implements Runnable (...) public void run() { Factory factory;

AW: AW: Some thoughts about classloaders

Pierre De Rop wrote: > Oups, your are right: in the step 2, I made a mistake, and typed "B" > instead of "A": > here is the fixed step 2: > > 2. If no Thread Context ClassLoader is set (null), then use the class > loader which loaded the XmlInputFactory class (that is: the class > loa

Re: Invalid BundleContext

Hi Jared, I have to admit, that I am out of explanations What you might do is add a log service to your framework and enable logging of bundle events (LogService implementations are specified to log these) and see when the respective bundle is stopped... Regards Felix jaredmac schrieb: >

Re: AW: Some thoughts about classloaders

Kevin Lohmann wrote: Thanks Pierre and Guillaume for your replies. I will give these ideas a try! @Pierre: Well, maybe the better way to understand what is going on is looking at the source code of the XMLInputFactory.newInstance(). I guess this method do something like the following: