Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 1 Oct 2012 13:16:07 +1100 (NCT)
From: "James Carman (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <808225454.146543.1349057767525.JavaMail.jiratomcat@arcas>
In-Reply-To: <114565048.145191.1348999027797.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CAMEL-5668) camel-jetty - A soap fault should
 trigger http response code 500
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

James Carman commented on CAMEL-5668:
-------------------------------------

We should really think about consolidating this code.  There are some value-adds in the http component that aren't in the http4 component.  They're virtually the same exact code.  There has to be a way to extract a superclass from this and create some abstract supermodule that they can both reference.
                
> 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
>
>         Attachments: CAMEL-5668.patch
>
>
> 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