Skip to content
This repository has been archived by the owner on Jan 30, 2019. It is now read-only.

Parsing of mustUnderstand header fails due to wrong namespaces #1684

Open
glassfishrobot opened this issue Mar 14, 2014 · 3 comments
Open

Parsing of mustUnderstand header fails due to wrong namespaces #1684

glassfishrobot opened this issue Mar 14, 2014 · 3 comments

Comments

@glassfishrobot
Copy link
Contributor

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]

@glassfishrobot
Copy link
Contributor Author

Reported by fschlier

@glassfishrobot
Copy link
Contributor Author

Was assigned to snajper

@glassfishrobot
Copy link
Contributor Author

This issue was imported from java.net JIRA WSIT-1684

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant