Hi Alexander, I just walked through the Discovery Demo as described here: http://cxf.apache.org/dosgi-discovery-demo-page.html and it works fine for me.
Looking at the source code where you get the exception: > java.lang.NullPointerException > at > org.apache.cxf.dosgi.discovery.zookeeper.Activator.updated(Activator.java:60) to me it seems like the updated() callback is made before the bundle.start() has returned. Hmmm, there might be a race condition here ... Is it possible for you to provide a test case that consistently fails? Otherwise, did you walk through the Discovery Demot page mentioned above? Does that work for you? Thanks, David 2009/12/7 Alexander Broekhuis <[email protected]>: > Hi all, > > When using the 1.1 release, I get a nullpointer if discovery is used: > > *ERROR* {org.osgi.service.cm. > ManagedService}={service.pid=org.apache.cxf.dosgi.discovery.zookeeper, > zookeeper.port=2181, zookeeper.timeout=3000, service.id=38}: Unexpected > problem updating configuration > java.lang.NullPointerException > at > org.apache.cxf.dosgi.discovery.zookeeper.Activator.updated(Activator.java:60) > at > org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:959) > at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:88) > > I used the 1.1 snapshot before, and never had this problem with discovery. > Is there something I forgot? > > I am using the singlebundle release with the latest (3.2.1) zookeeper. > > -- > Met vriendelijke groet, > > Alexander Broekhuis >
