You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Carman (JIRA)" <ji...@apache.org> on 2012/10/01 03:40:07 UTC
[jira] [Commented] (CAMEL-5668) camel-jetty - A soap fault should
trigger http response code 500
[ https://issues.apache.org/jira/browse/CAMEL-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466609#comment-13466609 ]
James Carman commented on CAMEL-5668:
-------------------------------------
I believe this is reported against the wrong component. The issue actually lies within the HTTP component in the DefaultHttpBinding class.
> camel-jetty - A soap fault should trigger http response code 500
> ----------------------------------------------------------------
>
> Key: CAMEL-5668
> URL: https://issues.apache.org/jira/browse/CAMEL-5668
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
> Affects Versions: 2.9.0, 2.10.0
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.9.4, 2.11.0, 2.10.2
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Help-with-nmr-cxf-endpoints-and-fault-handling-tp5719720.html
> If a response is fault=true, then we should force the http response code to be 500. Which is what the SOAP 1.1 spec mandates.
> See section 6.2 at: http://www.w3.org/TR/soap11/#_Ref477795996
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira