> Are they on crack?
Yes. :-) See: http://ws-i.org/profiles/basicprofile-1.2-2010-11-09.html#SOAPFAULT "A Fault is an envelope that has a single child element of the soap11:Body element, that element being the soap11:Fault element." If their Body has things in addition the fault, it's not WS-I Basic Profile compliant and I'd expect it not to work well at all. Dan On Friday, March 23, 2012 11:31:26 AM David Mansfield wrote: > Hi All: > > I'm using CXF 2.5.2 for a web-service client. In certain scenarios I > can generate a Fault response from the service I'm accessing, however > the actual response cannot be processed as it fails the > validation/unmarshal with: > > Caused by: javax.xml.bind.UnmarshalException: unexpected element > (uri:"http://xxx.com/XXX/Service/2009-11-06";, local:"messageHeader"). > Expected elements are <{}return> > > I believe they are in the wrong, because the actual content is indeed bad. > > What they are sending me is the soap:body from _my request_ with their > fault element appended. > > The response parser is expecting a valid response message as per the > wsdl / xml schema. > > Is there something wrong with my understanding of how fault's should be > handled? Are they on crack? > > Thanks, > David Mansfield > Cobite, INC. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
