-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.1.0
-
None
-
JBoss EAP 4.3.0.GA_CP07
JBossWS 2.0.1SP07
JBossWS 3.3.1GA
-
-
Due to an error in the SAAJ implementation in the JBossWS libraries, SOAP nodes previously had the same prefix as the <Envelope> node. This has been corrected, so that SOAP nodes now have their own prefix.
-
Documented as Resolved Issue
The SAAJ implementation in the JBossWS libraries is forcing all SOAP-nodes to have the same prefix as the <Envelope> node.
With current native saaj implementation to create soap message from this string :
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><S:Header xmlns:S='http://schemas.xmlsoap.org/soap/envelopes'></S:Header><S:Body xmlns:S='http://schemas.xmlsoap.org/soap/envelopes'> <ns1:addItemResponse xmlns:ns1='http://org.jboss.ws/addressing/replyto'> <result>Mars Bar</result> </ns1:addItemResponse> </S:Body></env:Envelope>
The created soap header and soap body are with prefix "env" . This caused some problem when ws security is enabled and soap header or body part is signed.
- blocks
-
JBPAPP-4552 Release and upgrade JBossWS Native
- Closed
- clones
-
JBPAPP-5700 CLONE - [JBossWS] SAAJ implementation does not set the correct NS prefix in SOAP header and body elements
- Resolved
- incorporates
-
JBWS-3159 SAAJ implementation does not set the correct NS prefix in SOAP header and body elements
- Closed