[CXF-1849] PolicyVerificationOutInterceptor writes faults at wrong phase when processing response

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.1.3
• Component/s: WS-* Components
• Assignee: Daniel Kulp
• Reporter: Fred Dushin
• Created: 08/Oct/08 10:11
• Updated: 23/Jan/09 17:53
• Resolved: 10/Oct/08 18:34

Description

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>