Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006H4xF&sfdc.override=1 project_key: SOA SOAPFactoryImpl forces namespace declarations to be added for all child elements which are not immediate descendants of the element declaring the namespaces. This is seen in ESB as a consequence of adding a Document to the soap body. For example <say:sayHiResponse xmlns:say='http://www.jboss.org/sayHi' xmlns:say2='http://www.jboss.org/sayHi2'> <say2:arg0> <say2:arg2>Response</say2:arg2> </say2:arg0> </say:sayHiResponse> will be created as <say:sayHiResponse xmlns:say='http://www.jboss.org/sayHi' xmlns:say2='http://www.jboss.org/sayHi2'> <say2:arg0> <say2:arg2 xmlns:say2='http://www.jboss.org/sayHi2'>Response</say2:arg2> </say2:arg0> </say:sayHiResponse>
Simple demonstration of issue.
Attachment: Added: NamespaceIssue.java
Link: Added: This issue is a dependency of JBPAPP-5866
Link: Added: This issue depends JBPAPP-5866
Link: Removed: This issue is a dependency of JBPAPP-5866
Should be in builds we pick up from EAP 5.1.2 sources.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: JBossWS native adds additional namespaces upon output when documents have been added to the SOAP body. SOAPFactoryImpl forces namespace declarations to be added for all child elements which are not immediate descendants of the element declaring the namespaces.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.