>> - RepositoryAdmin got set, the removed, then set, which caused an NPE >> in one of our declared service classes
> Not sure I have enough information to comment on this. Can you explain it > more? I make no defense of the code (it's terrible, and has been rewritten), but I've attached the deployed version. When the RepositoryAdmin has been set, it spawns a thread that works with it. However, that instance variable gets nulled out by an immediate removeRepoAdmin() method call, which then causes the NPE. Since that's on a whole other thread, it shouldn't have any impact on startup, right? Anyway, the real question may be why it is getting set, then unset, then set again. >> - logging seemed to be going through a mix of PAX-logging and the >> default Felix logger > Well, we were running into some deadlocking issues when Felix was calling > out to external Log Services, so for now we disabled that feature since it > was causing difficulties for people. So how do I turn that off? I'm seeing thousands of ClassNotFoundExceptions and Missing Resources, that are not errors, coming out of Spring and JavaFX and javax.beans and some custom bundles... For example: (scanning all bundles for certain files): WARNING: config.txt (org.apache.felix.moduleloader.ResourceNotFoundException: config.txt) WARNING: bundle.zip (org.apache.felix.moduleloader.ResourceNotFoundException: bundle.zip) (using spring and spring-dm): WARNING: org.springframework.beans.factory.xml.NamespaceHandler (java.lang.ClassNotFoundException: org.springframework.beans.factory.xml.NamespaceHand ler) WARNING: org.osgi.framework.ServiceReference (java.lang.ClassNotFoundException: org.osgi.framework.ServiceReference) >> - we could no longer load images from a Class.getResource() URL like >> bundle://56.0:1/org/bjc/pt2/i18n/mock/background.png > Not sure why that would be the case. Again, we probably need more specific > details. Basically, we have an i18n bundle that constructs a Swing ImageIcon for us, based on a URL. That ImageIcon is passed to other bundles, but it shouldn't have any trouble loading data from that URL, since it was created by the same bundle. > I would say upgrading definitely makes sense. You probably even should > consider Felix 1.2.0 which is currently under vote for release now. We'd like to be as up-to-date as possible, as this is a moderately painful process for us. How far is 1.2.0 from release? Thanks, Pat. -- Defy mediocrity.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
