[
https://issues.apache.org/jira/browse/CXF-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jervis Liu resolved CXF-632.
----------------------------
Resolution: Fixed
> When handleMessage() returns false, we need to reverse the message direction,
> and if its outbound, we need to stop outbound processing and send the msg
> back to its sender
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-632
> URL: https://issues.apache.org/jira/browse/CXF-632
> Project: CXF
> Issue Type: Sub-task
> Reporter: Jervis Liu
> Assigned To: Jervis Liu
>
> When handleMessage() returns false, we need to reverse the message direction,
> and if its outbound, we need to stop outbound processing and send the msg
> back to its sender
> See JAX-WS spec 9.3.2.1:
> Return false This indicates that normal message processing should cease.
> Subsequent actions depend on whether the message exchange pattern (MEP) in
> use requires a response to the message currently being processed2 or not:
> Response The message direction is reversed, the runtime invokes handleMessage
> on the next handler or dispatches the message (see section 9.1.2.2) if there
> are no further handlers.
> In order to do this, we need a mechanism that can stop the outbound
> intercetor chain, set inbound message to be the message that has been
> processed by handlers' handlerMessage(), start an inbound intercetor chain.
> However this kind of APIs are not in place yet, the only way to stop
> interceptor chain is to throw an exception then start fault chain.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
