cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Grzybek (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-5630) In robust one-way fault the fault message should result in SOAPFaultException
Date Fri, 21 Mar 2014 19:23:43 GMT

    [ https://issues.apache.org/jira/browse/CXF-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943420#comment-13943420
] 

Grzegorz Grzybek edited comment on CXF-5630 at 3/21/14 7:22 PM:
----------------------------------------------------------------

You're right - the spec should allow this. But all depends on mysterious TCK developers whether
they used {{instanceof}} or {{Class.equals(Class other)}} :)

Anyway - I checked that in debug session:
* I set contextual property on {{((Client)greeter).getEndpoint().put(Message.ROBUST_ONEWAY,
true)}}
* While handling the response in HTTPConduit I tweaked the code to check the flag and not
go into {{if (oneway) \{...\}}} block - the exception was then constructed as {{SOAPFaultException}}

OK, I'll reopen it and think about it tomorrow.


was (Author: gzres):
You're right - the spec should allow this. But all depends on mysterious TCK developers whether
they used {{instanceof}} or {{Class.equals(Class other)}} :)

Anyway - I checked that in debug session:
* I set contextual property on {{((Client)greeter).getEndpoint().put(Message.ROBUST_ONEWAY,
true)}} (or something like this, I can't tell from memory)
* While handling the response in HTTPConduit I tweaked the code to check the flag and not
go into {{if (oneway) \{...\\}}} block - the exception was constructed as {{SOAPFaultException}}

OK, I'll reopen it and think about it tomorrow.

> 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)

Mime
View raw message