[
https://issues.apache.org/jira/browse/CXF-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943566#comment-13943566
]
Daniel Kulp commented on CXF-5630:
----------------------------------
Did you check the code on trunk/2.7.x-fixes? I did fix the HTTPConduit to
check the ROBUST_ONEWAY flag.
Since the TCK would never set the ROBUST_ONEWAY flag as that's a proprietary
flag, the change in HTTPConduit would have no effect on the TCK.
> 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)