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/02/05 04:38:05 UTC
[jira] Closed: (CXF-333) Logical handler throws ProtocolException
[ https://issues.apache.org/jira/browse/CXF-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jervis Liu closed CXF-333.
--------------------------
Resolution: Fixed
> Logical handler throws ProtocolException
> ----------------------------------------
>
> Key: CXF-333
> URL: https://issues.apache.org/jira/browse/CXF-333
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-WS Runtime
> Reporter: Jervis Liu
> Attachments: cxf-333.patch
>
>
> According to spec, when logical handler throws ProtocolException, JAX-WS 9.3.2.1:
> Throw ProtocolException or a subclass This indicates that normal message processing should cease. 27
> Subsequent actions depend on whether the MEP in use requires a response to the message currently 28
> being processed or not:
> Response Normal message processing stops, fault message processing starts. The message direction 1
> is reversed, if the message is not already a fault message then it is replaced with a fault message4, 2
> and the runtime invokes handleFault on the next4 handler or dispatches the message (see 3
> section 9.1.2.2) if there are no further handlers. 4
> No response Normal message processing stops, close is called on each previously invoked handler 5
> in the chain, the exception is dispatched (see section 9.1.2.3).
> Our current implementation does not conform to this yet. See two commented out test: HandlerInvocationTest.testLogicalHandlerThrowsProtocolExceptionClientSide() and HandlerInvocationTest.xtestLogicalHandlerThrowsProtocolExceptionServerSide
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.