[
https://jira.jboss.org/jira/browse/JBWS-2940?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2940:
----------------------------------
Summary: Wrong SOAPContentElement namespace prefix after multiple model
transitions (was: 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)
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 achieved parsing the fragment to the container element. This
breaks messages in some subtle cases because the SOAPContentElement prefix is not updated.
(was: Fix for JBPAPP-3785)
Wrong SOAPContentElement namespace prefix after multiple model
transitions
--------------------------------------------------------------------------
Key: JBWS-2940
URL:
https://jira.jboss.org/jira/browse/JBWS-2940
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Magesh Kumar B
Assignee: Alessio Soldano
Fix For: jbossws-native-3.3.0.Beta5
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 achieved parsing the fragment to the container element. This
breaks messages in some subtle cases because the SOAPContentElement prefix is not updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira