Dan,
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. > Since it's late Sunday evening here and the kids need to go to bed, I'll do that first thing tomorrow morning in the office. I downloaded apache-cxf-2.2.7-SNAPSHOT-src.zip to take look. I'm not familiar with maven, but from reading BUILDING.txt I conclude that is not really necessary. Can I work with this file or do I need a more recent version (date was Sat Mar 13 07:50:14 GMT+00:00 2010)? dkulp wrote: > > The second stack trace is also a bit strange. It's an NPE in LinkedList > which is very strange. Normally, JAXB uses ArrayLists for pretty much > everything so I'm not sure why a LInkedList is there. Do you have some > custom JAXB beans or something there that would be using LinkedList > instead? > The service response can contain a list of messages which is a LinkedList<String> in the annotated interface. Should we better use the List type (probably yes...)? Thanks, Michael -- View this message in context: http://old.nabble.com/Concurrency-issue-tp27882337p27897722.html Sent from the cxf-user mailing list archive at Nabble.com.
