You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2019. It is now read-only.
When using wsit the SOAP message headers are parsed using the com.sun.xml.ws.security.opt.impl.incoming.GenericSecuredHeader on the webservice provider side for incomming messages. The parsing of the header attributes is split up for SOAP 1.1/1.2 in the methods process11Header/process12Header.
Inside of these methods, the process11Header uses the 1.2 namespace for parsing the attributes like mustUnderstand and vice versa.
As a consequence the mustUnderstand flags are always remaining on the default false and later on assertion are not executed. An unknown header, flagged with mustUnderstand="true" is silently ignored.
Environment
Windows 2008 R2, Tomcat 7.0.32, jaxws-rt-2.2.8
Affected Versions
[2.3]
The text was updated successfully, but these errors were encountered:
When using wsit the SOAP message headers are parsed using the com.sun.xml.ws.security.opt.impl.incoming.GenericSecuredHeader on the webservice provider side for incomming messages. The parsing of the header attributes is split up for SOAP 1.1/1.2 in the methods process11Header/process12Header.
Inside of these methods, the process11Header uses the 1.2 namespace for parsing the attributes like mustUnderstand and vice versa.
As a consequence the mustUnderstand flags are always remaining on the default false and later on assertion are not executed. An unknown header, flagged with mustUnderstand="true" is silently ignored.
Environment
Windows 2008 R2, Tomcat 7.0.32, jaxws-rt-2.2.8
Affected Versions
[2.3]
The text was updated successfully, but these errors were encountered: