Details
-
Bug
-
Resolution: Done
-
Major
-
jbossws-native-3.1.2
-
None
Description
This was spotted because of JBPAPP-3785. Basically the problem is when moving from XML_VALID to DOM_VALID state of the model, the Native stack can end up with a wrong namespace assigned to the SOAPContentElement of the body. That's possible when a previous transition from OBJ_VALID to XML_VALID has caused JAXB to marshall the content to a new xml fragment that despite being equivalent to the original content has different namespace <--> prefix associations. When later moving to DOM_VALID, attributes are copied from the element obtained parsing the fragment to the container element. This breaks messages in some subtle cases because the SOAPContentElement prefix is not updated.
Attachments
Issue Links
- is incorporated by
-
JBPAPP-3785 Wrong namespace on SOAP operation when a method with header parameter having a new namespace is invoked, "second" after a method that does not have this namespace'd parameter
- Closed
- relates to
-
JBWS-2962 Sign/encrypt verification can fail when the soap model performs transition during it
- Closed