cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jervis Liu (JIRA)" <>
Subject [jira] Commented: (CXF-333) Logical handler throws ProtocolException
Date Mon, 05 Feb 2007 03:36:05 GMT


Jervis Liu commented on CXF-333:

Done by Unreal

> Logical handler throws ProtocolException
> ----------------------------------------
>                 Key: CXF-333
>                 URL:
>             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
> 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
> section 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
> 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.

View raw message