DOMWriter given any arbitrary DOM element from the the tree should produce valid XML. i.e. it must include the NS declarations from further up if they are not defined on the element that is beeing written out. Previous to the change to DOMWriter, the SOAP content element was beeing assigned invalid XML, which had to be corrected before the fragment was passed to JBossXB. If NS declarations are duplicated on nested elements that would be an error. Correct is, that every XML fragment associated with a SOAPContentElement is valid, which leads to NS declarations on #1 SOAPBodyElement for doc/lit and #2 RPC params for rpc/lit #3 SOAPHeader elements The DOMWriterTestCase should comperensivly test the correct behaviour of the DOMWriter. The XML fragment association may go away in future http://jira.jboss.org/jira/browse/JBWS-1314 when we no longer need to pass XML fragments to JBossXB (i.e can work with DOMSource for example) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979945#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...