[
https://issues.apache.org/jira/browse/TUSCANY-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-3838.
-------------------------------
I believe this is fixed now. The policy runtime is slightly different in 2.x
when compared to 1.x. In 2.x we have policy interceptors on the operation wire
and on the binding wire and the binding wire providers get the opportunity to
configure the binding. In the exception case the exception, wrapped in a
Message object, should flow back along the wire and through the interceptors in
the same way as a non-exception response does.
> PolicyHandler.afterInvoke() is skipped when AxisFault occurs
> ------------------------------------------------------------
>
> Key: TUSCANY-3838
> URL: https://issues.apache.org/jira/browse/TUSCANY-3838
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Policy
> Affects Versions: Java-SCA-1.6
> Environment: Windows 2003.
> Reporter: Gang Yang
> Assignee: Simon Nash
> Fix For: Java-SCA-1.x
>
> Attachments: code-snippet.txt
>
>
> When AxisFault is generated from invoking a remote service using WS binding,
> the reference side PolicyHandler.afterInvoke() is not called.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
