You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jervis Liu (JIRA)" <ji...@apache.org> on 2007/05/03 05:46:15 UTC
[jira] Created: (CXF-630) When handleMessage throws
ProtocolException, the Message should be replaced with a fault Message
When handleMessage throws ProtocolException, the Message should be replaced with a fault Message
------------------------------------------------------------------------------------------------
Key: CXF-630
URL: https://issues.apache.org/jira/browse/CXF-630
Project: CXF
Issue Type: Sub-task
Components: JAX-WS Runtime
Reporter: Jervis Liu
Assigned To: Jervis Liu
JAX-WS 9.3.2.1:
Throw ProtocolException or a subclass This indicates that normal message processing should cease.
Subsequent actions depend on whether the MEP in use requires a response to the message currently
being processed or not:
Response Normal message processing stops, fault message processing starts. The message direction
is reversed, if the message is not already a fault message then it is replaced with a fault message,
and the runtime invokes handleFault on the next handler or dispatches the message (see
section 9.1.2.2) if there are no further handlers.
See test case:HandlerChainInvokerTest.testHandleMessageThrowsProtocolExceptionWithResponseExpected()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-630) When handleMessage throws
ProtocolException, the Message should be replaced with a fault Message
Posted by "Jervis Liu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jervis Liu closed CXF-630.
--------------------------
> When handleMessage throws ProtocolException, the Message should be replaced with a fault Message
> ------------------------------------------------------------------------------------------------
>
> Key: CXF-630
> URL: https://issues.apache.org/jira/browse/CXF-630
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-WS Runtime
> Reporter: Jervis Liu
> Assigned To: Jervis Liu
>
> JAX-WS 9.3.2.1:
> Throw ProtocolException or a subclass This indicates that normal message processing should cease.
> Subsequent actions depend on whether the MEP in use requires a response to the message currently
> being processed or not:
> Response Normal message processing stops, fault message processing starts. The message direction
> is reversed, if the message is not already a fault message then it is replaced with a fault message,
> and the runtime invokes handleFault on the next handler or dispatches the message (see
> section 9.1.2.2) if there are no further handlers.
> See test case:HandlerChainInvokerTest.testHandleMessageThrowsProtocolExceptionWithResponseExpected()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-630) When handleMessage throws
ProtocolException, the Message should be replaced with a fault Message
Posted by "Jervis Liu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jervis Liu resolved CXF-630.
----------------------------
Resolution: Fixed
> When handleMessage throws ProtocolException, the Message should be replaced with a fault Message
> ------------------------------------------------------------------------------------------------
>
> Key: CXF-630
> URL: https://issues.apache.org/jira/browse/CXF-630
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-WS Runtime
> Reporter: Jervis Liu
> Assigned To: Jervis Liu
>
> JAX-WS 9.3.2.1:
> Throw ProtocolException or a subclass This indicates that normal message processing should cease.
> Subsequent actions depend on whether the MEP in use requires a response to the message currently
> being processed or not:
> Response Normal message processing stops, fault message processing starts. The message direction
> is reversed, if the message is not already a fault message then it is replaced with a fault message,
> and the runtime invokes handleFault on the next handler or dispatches the message (see
> section 9.1.2.2) if there are no further handlers.
> See test case:HandlerChainInvokerTest.testHandleMessageThrowsProtocolExceptionWithResponseExpected()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.