[
https://issues.apache.org/jira/browse/CXF-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943424#comment-13943424
]
Grzegorz Grzybek edited comment on CXF-5630 at 3/21/14 7:22 PM:
----------------------------------------------------------------
Everything depends on interpretation of JAX-WS 2.2:
{quote}
Conformance (Failed Dispatch.invokeOneWay):
When an operation is invoked using an invoke-OneWay method, an implementation
MUST throw a WebServiceException. if there is any error in the configuration of
the Dispatch instance or if an error is detected during the remote operation
invocation.
{quote}
and it depends on TCK (I wonder if I live to see JavaEE TCKs available on
GitHub...) of course.
was (Author: gzres):
Everything depends on interpretation of:
{quote}
Conformance (Failed Dispatch.invokeOneWay):
When an operation is invoked using an invoke-OneWay method, an implementation
MUST throw a WebServiceException. if there is any error in the configuration of
the Dispatch instance or if an error is detected during the remote operation
invocation.
{quote}
and it depends on TCK (I wonder if I live to see JavaEE TCKs available on
GitHub...) of course.
> In robust one-way fault the fault message should result in SOAPFaultException
> -----------------------------------------------------------------------------
>
> Key: CXF-5630
> URL: https://issues.apache.org/jira/browse/CXF-5630
> Project: CXF
> Issue Type: Bug
> Reporter: Grzegorz Grzybek
> Assignee: Daniel Kulp
> Fix For: 3.0.0, 2.7.11
>
>
> Now in
> {{org.apache.cxf.transport.http.HTTPConduit.WrappedOutputStream.handleResponseInternal()}}
> there's just one check if the exchange is one-way without checking the
> "robust" status and if exchange is one way, any soap fault is consumed.
> I'm not sure how this should be handled, as _robustnes_ is not defined per
> SOAP 1.1
--
This message was sent by Atlassian JIRA
(v6.2#6252)