-
Bug
-
Resolution: Done
-
Major
-
EAP 5.0.1
-
None
-
-
SOAPFactoryImpl forces additional namespace declarations in all child elements that are not immediate child elements of the element declaring the namespaces. This explicit declaration is redundant and is now no longer added.
-
Documented as Resolved Issue
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>
- blocks
-
JBPAPP-6268 Release and upgrade JBossWS Native for EAP 5.1.2
-
- Closed
-
- incorporates
-
JBWS-3209 JBossWS native adds additional namespace declarations to output
-
- Closed
-