[
https://issues.apache.org/jira/browse/WSS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706945#comment-13706945
]
Daniel Kulp commented on WSS-459:
---------------------------------
This is definitely going to have issues in both CXF (when using
Provider<Source> and Dispatch<Source>) and in Camel with PAYLOAD mode. Those
all pretty much pass the XMLStreamReader directly to the target where they are
consumed (or not) depending on the requirements there.
Not really sure what to do.... Can we possibly have a "prevalidate()" method
or something added to the reader that can at least do some minimal validation
of the headers to detect this prior to the call into the user code? Actually,
once the soap:Body or soap:Header closing tag is hit, the reader could likely
check the headers existence and throw exceptions. That said, if something
requires a particular element in the body someplace, that wouldn't be
detectable until the close.
> RequiredParts + EncryptedParts policy validation not working
> ------------------------------------------------------------
>
> Key: WSS-459
> URL: https://issues.apache.org/jira/browse/WSS-459
> Project: WSS4J
> Issue Type: Bug
> Reporter: Colm O hEigeartaigh
> Assignee: Marc Giger
> Fix For: 2.0
>
>
> RequiredParts policy validation is not working. A CXF negative test-case
> (StaxPartsTest) has a policy which "requires" a header of name "ToTo",
> however the (streaming) service throws no error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
