ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Commented] (WSS-459) RequiredParts + EncryptedParts policy validation not working
Date Fri, 12 Jul 2013 13:53:52 GMT


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:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message