[
https://issues.apache.org/jira/browse/CXF-8945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8945:
------------------------------
Description: In case of JAX-WS oneway operation, the out interceptor chain
in not called at all on client side. This is somewhat expectable since there
is no out message to go through, however it makes some features (like tracing
for example) harder to implement since the start interceptor is called, but not
the stop one. It would be great to have a mechanism that signals that the
invocation is done for one way calls. (was: In case of oneway operation, there
out interceptor chain in not called at all. This is somewhat expectable since
there is no out message to go through, however it makes some features (like
tracing for example) harder to implement since the start interceptor is called,
but not the stop one. It would be great to have a mechanism that signals that
the invocation is done for one way calls.)
> [JAX-WS] The client out interceptor chain is not called in case of oneway
> operation
> -----------------------------------------------------------------------------------
>
> Key: CXF-8945
> URL: https://issues.apache.org/jira/browse/CXF-8945
> Project: CXF
> Issue Type: Bug
> Reporter: Andriy Redko
> Assignee: Andriy Redko
> Priority: Major
>
> In case of JAX-WS oneway operation, the out interceptor chain in not called
> at all on client side. This is somewhat expectable since there is no out
> message to go through, however it makes some features (like tracing for
> example) harder to implement since the start interceptor is called, but not
> the stop one. It would be great to have a mechanism that signals that the
> invocation is done for one way calls.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
