Can you create a sample that demonstrates this? Can you also test with the latest 2.5.3-SNAPSHOT? Also, is there anything "interesting" in the logs?
The symptom is very similar to https://issues.apache.org/jira/browse/CXF-4106 where attachments were getting "lost" due to the SoapBodyInfo and other mime things getting "lost". I'd like to know if something in the logs was saying "could not find service..." or other message that would indicate it was creating a new binding. If so, 2.5.3-SNAPSHOT *MIGHT* already fix it. Dan On Wednesday, March 21, 2012 01:57:40 PM Dickerson, Kyle B. wrote: > This topic was previously: "CXF as Client - Response Attachment - > HolderInInterceptor IndexOutOfBoundsException" > > But this subject better represents the true issue > > > > SwAInInterceptor is failing to handle the attachment because SoapBodyInfo > is null. > > The relevant code from SwAInInterceptor.java is: > > > > BindingOperationInfo bop = message.getExchange().getBindingOperationInfo() > > if (bop.isUnwrapped()) {bop = bop.getWrappedOperation()} > > boolean client = isRequestor(message) // client == true > > BindingMessageInfo bmi = client ? bop.getOutput() : bop.getInput() > > SoapBodyInfo sbi = bmi.getExtensor(SoapBodyInfo.class) > > > > sbi is null at this point and a null check stops execution. So > messageContentsList is not populated with the attachment as it should be. > > > > Using reflection to investigate the BindingMessageInfo object I learn: > > 1. No delegate is in use. > > 2. The only extensor available is "SOAPBody > ({http://schemas.xmlsoap.org/wsdl/soap/}body): required=null > use=literal". > > 3. Don't know if this is relevant, if I ask the SOAPBody extensor its > class I get "$Proxy42" > > > > Since no extensor match is found for a SoapBodyInfo class we get a null > value returned, so sbi is null. > > > > Anyone have any thoughts on why SoapBodyInfo is coming back null? > > > > Thanks, > > Kyle -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
