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

kanagamahendran Velusamy commented on CXF-4241:
-----------------------------------------------

This is request-response service:
when the server sends the soap fault with 400 http code this is what the error 
we get from CXF

javax.xml.ws.WebServiceException: Could not send Message.
        at 
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
        at $Proxy41.updateUserProfile(Unknown Source)
        at com.payconnexion.ws.client.PConClient.main(PConClient.java:72)
Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '400: Bad 
Request' when communicating with https://ws.vitechinc.com
        at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1502)
        at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1448)
        at 
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1356)
        at 
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
        at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:614)
        at 
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
        at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:484)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:414)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:317)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:269)
        at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
        at 
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
        ... 2 more

What we receive is the perfect soap fault message,unfortunately CXF doesnt 
translate to soap fault instead of Exception.


                
> Http Conduit doesnt honor soap fault if server sends with 400 or 500 error
> --------------------------------------------------------------------------
>
>                 Key: CXF-4241
>                 URL: https://issues.apache.org/jira/browse/CXF-4241
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.4.6
>         Environment: Linux;JDK 1.6.25
>            Reporter: kanagamahendran Velusamy
>              Labels: conduit, http
>
> We have a situation where server sends Soap-fault with 400(http error) 
> however cxf throws exception saying that "400: Bad Request" without the 
> details of the message. 
> my point is, even though server sends 400 or 500, CXF should read the message 
> and if it is soap fault,it should construct soap fault not just the exception 
> . in this way we are not restricting server to send the soap fault in 200 OK 
> level.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to