[CXF-4652] Additional namespace is added when web service provider implements Provider<DOMSource>

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.2
• Fix Version/s: 2.5.7, 2.6.4, 2.7.1

Environment

win7 + oracle jdk 1.6.0_29-b11

• Estimated Complexity: Unknown
• Assignee: Freeman Yue Fang
• Reporter: Hong Fang Han
• Created: 26/Nov/12 05:57
• Updated: 16/Jul/13 19:28
• Resolved: 26/Nov/12 09:13

Description

In the invoke method of web service provider which implements Provider<DOMSource>, using the following code to return a response DOMSource,

DOMSource response = new DOMSource();
DocumentBuilderFactory documentFacory = DocumentBuilderFactory.newInstance();
DocumentBuilder documentBuilder = null;
try

{ documentBuilder = documentFacory.newDocumentBuilder(); }

catch (ParserConfigurationException e)

{ throw new RuntimeException(e); }

Document doc;
try

{ doc = documentBuilder.parse(new InputSource( new ByteArrayInputStream(message.getBytes("UTF-8")))); }

catch (Exception e)

{ throw new RuntimeException("error parse: " + str, e); }

response.setNode(doc);

In above code, if message string is:

"<ns2:echoResponse xmlns:ns2="annotations.webserviceprovider.fq"><return>Hello world</return></ns2:echoResponse>",

but the soapMessage body will be:

"<ns2:echoResponse xmlns:ns2="annotations.webserviceprovider.fq" xmlns="annotations.webserviceprovider.fq"><return>Hello world</return></ns2:echoResponse>"

Additional attribute xmlns="annotations.webserviceprovider.fq" is added by cxf. This additional attribute causes the unmarshal issue at client side.