 <blockquote> <p>Is there any way to get a response without the target namespace?</p> </blockquote> <p>I hope not. A SOAP web service should have a well-defined, published interface and every response that it sends should conform to that interface. Usually, the interface is described by a WSDL document.</p> <blockquote> <p>And would like to get it without the target namespace</p> </blockquote> <pre><code>&lt;MyItem&gt; &lt;class&gt;myClass&lt;/class&gt; &lt;name&gt;MyItemName&lt;/name&gt; &lt;/MyItem&gt; </code></pre> <p>Being pedantic, but the absence of a namespace prefix does not mean that there is no namespace. There might be a default namespace in force. So you <em>could</em> achieve XML that looks exactly like the above and the MyItem, class and name tags might still have a non-empty namespace.</p> <blockquote> <p>I know its purpose and that it's actually quite useful.</p> </blockquote> <p>The purpose of a namespace in an XML document ( whether a web service response, or any other XML ) is to avoid polluting the global namespace. Do you really want 'name' and 'class' to have exactly one meaning in your applications? Or would it be better if each schema could define its own version of those?</p> <blockquote> <p>But it happened that it can't be processed any further by another tool with this target namespace and looks like this: </p> </blockquote> <pre><code>&lt;MyItem xmlns="http://spring.io/guides/gs-producing-web-service"&gt; ... </code></pre> <p>That looks like valid XML, so what's the problem? Is that output produced by the 'other tool'? Or is it something that the 'other tool' cannot handle?</p>