On Aug 23, 2012, at 3:29 PM, kbabushkin <[email protected]> wrote:
> Hi Daniel, > > Send sample to your email… It's definitely the WSDL. The wsdl uses various types from the soap/w attachment schemas and spec: http://ws-i.org/profiles/basic/1.1/swaref.xsd …. <xs:element minOccurs='0' name='wavFile' type='swaRef:swaRef'/> etc… With that, we have to setup the attachment stuff "just in case" as we won't know ahead of time whether the types will be hitting the attachment stuff or not. The only workaround I have right now is to remove the SwaOutInterceptor: Client client = ClientProxy.getClient(port); for (Interceptor<?> i : client.getEndpoint().getOutInterceptors()) { if (i instanceof SwAOutInterceptor) { client.getEndpoint().getOutInterceptors().remove(i); } } which is where we check the JAXBContext to see if swa is used or not. However, if you then invoke one of the operations for which it's required, you'll likely have other failures as the attachments won't be able to be written. Dan > > Many thanks, > Konstantin > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Apache-CXF-2-6-1-Client-gets-Content-is-not-allowed-in-prolog-tp5713009p5713049.html > Sent from the cxf-dev mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
