For reference (possible other workaround?): the NPE disappeared after adding the org.apache.cxf.interceptor.StaxOutInterceptor to the out client interceptors
Lukasz L. wrote: > > We have a similar issue with Dispatch style service client. The workaround > proposed here does not work because msg.getContent(List.class) returns > null. > Any other ideas? > Is WS-Security supported with Dispatch invocation? How to make it work? > > > Lee Breisacher-2 wrote: >> >> For the record, the fix for this NPE is trivial, and this single fix >> seems to be all that's needed -- WS-S seems to work fine after just this >> one fix. I added this to my subclass of WSS4JOutInterceptor: >> >> SOAPMessage sm = (SOAPMessage) >> msg.getContent(List.class).get(0); >> msg.setContent(SOAPMessage.class, sm); >> super.handleMessage(msg); >> >> Lee >> > > -- View this message in context: http://www.nabble.com/NPE-when-using-WSS4JOutInterceptor-tp19654161p21287330.html Sent from the cxf-user mailing list archive at Nabble.com.
