Hi all, In our application we use CXF (among other things) to handle our webservices based on our java classes. Since we upgraded to CXF 2.7.10 the exact same request that worked in 2.7.7 now causes UnmarshallingErrors. This doesn't exist when using (for example) soapui to generate the requests as soapui handles explicit namespaces correctly but Axis 1.4 generates some funky (but valid) XML that repeatedly redefines the default namespace, which causes CXF to choke. I've been able to whittle the generating version down to 2.7.9 as this problem doesn't exist in CXF 2.7.8 but does exist in CXF 2.7.9 but I have unfortunately been unable to determine the exact cause.
The request SoapUI generates based on the wsdl and which works in every version of CXF is: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wis="http://wis.webservices.example.nl/";> <soapenv:Header/> <soapenv:Body> <wis:getStudent> <studentNumber>?</studentNumber> </wis:getStudent> </soapenv:Body> </soapenv:Envelope> However, one of our larger third-party clients uses Axis 1.4 to generate requests which look like: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wis="http://wis.webservices.example.nl/";> <soapenv:Header/> <soapenv:Body> <getStudent xmlns="http://wis.webservices.iridium.topicus.nl/";> <studentNumber xmlns="">115188</studentNumber> </getStudent> </soapenv:Body> </soapenv:Envelope> CXF 2.7.8 accepts this request and gives the correct response, however CXF 2.7.9 and 2.7.10 both give the following error: Unmarshalling Error: unexpected element (uri:"http://wis.webservices.example.nl/";, local:"studentNumber"). Expected elements are <{}studentNumber> Both soapUI as well as http://www.w3schools.com/xml/xml_validator.asp and http://www.xmlvalidation.com/ validate the XML so we believe the second request is a correct request (though perhaps a bit unwieldy with redefining the default namespace) and CXF shouldn't choke on it. Do you agree? If so, is there already a bug for this? We haven't been able to find one. Can you advise us on how best to create an issue for this (or can you create an issue for us) and perhaps help define which issue is the cause of this problem. Regards, Sven Haster Topicus BV Postbus 317 7400 AH Deventer Leeuwenbrug 23 (bezoekadres) T. +31 (0)6 3400 9545 T. +31 (0)570 662 662 E. [email protected]<mailto:[email protected]> I. http://www.topicus.nl
