Dan, Sorry for the late reply. Please find attached the stack traces produced with today's SNAPSHOT:
http://old.nabble.com/file/p27907080/cxf-concurrency-SNAPSHOT-20100315.txt cxf-concurrency-SNAPSHOT-20100315.txt Next thing I try here is remove optional jars which are still on the classpath. Michael dkulp wrote: > > > Interesting. In the first case, the line in question is just: > getBus().getExtension(WSDLManager.class).getExtensionRegistry(); > > Thus, either the Bus is null (would be strange) or the WSDLMananger is > null, > which also be bizarre. If changed the code to split that into three > lines. > Tomorrows snapshot will have that (or, if you could checkout the code and > build yourself to test, that would be great). I'd like to know which > line > would now have the NPE so I can try and figure out if it's the bus or the > wsdlmanager which is null. That would at least give me a clue where to > look. > > Dan > -- View this message in context: http://old.nabble.com/Concurrency-issue-tp27882337p27907080.html Sent from the cxf-user mailing list archive at Nabble.com.
