PolicyVerificationOutInterceptor writes faults at wrong phase when processing
response
--------------------------------------------------------------------------------------
Key: CXF-1849
URL: https://issues.apache.org/jira/browse/CXF-1849
Project: CXF
Issue Type: Bug
Components: WS-* Components
Affects Versions: 2.1.2
Reporter: Fred Dushin
Fix For: 2.1.3, 2.2
When a CXF response is processed on an endpoint that contains policy assertions
(via spring, WSDL, etc), and the policy assertions are not marked as asserted,
the PolicyVerificationOutInterceptor properly raises a SOAP fault. However,
this interceptor is inserted into the "post-stream" phase, and it seems as
though the fault gets written to the SOAP body after the business logic has
been written.
So a response in this scenario will come out as follows:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
<soap:Body>
<sayHiResponse xmlns="...">
<responseType>Bonjou</responseType>
</sayHiResponse>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>These policy alternatives can not be satisfied:
[snip]</faultstring >
</soap:Fault>
</soap:Body>
</soap:Envelope>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
