On Mon, Sep 24, 2012 at 4:28 PM, tnk <jus...@gmail.com> wrote: > Hi, > > sorry, maybe the situation wasn't clear enough. I have a simple jetty http > endpoint, which accepts requests and simply forwards it to nmr endpoint. > > > > And then, there is a cxfEndpoint (configuration in first post), listening to > nmr:fatal:endpoint and simple camel route: > > > fatalProcessor just throws Fault defined in wsdl. I can see in logs, that > soap fault is returned from CXF endpoint: > > > Then this fault is returned to webservice caller (in "consumerRoute"), but > http response code is 200 (although Response-Code 500 returned from nmr > endpoint). The strange thing, I can't do anything after the line "<camel:to > uri="nmr:fatal:endpoint" />", route is not executed further, camel treats > soap fault as exception (so why http 200 returned?) > The other case, then I throw RuntimeException (or call WS with invalid xml) > in fatalProcessor bean. cxfEndpoint returns soapfault as well, but the > result of "consumerRoute" to web service consumer is http response-code 500 > and exception stacktrace, although cxfEndpoint returns marshalled soap > fault: >
Yeah I think that this is a bug. A soap fault should be an http response code 500, as stated in section: 6.2 SOAP HTTP Response http://www.w3.org/TR/soap11/#_Ref477795996 I have logged a ticket about this https://issues.apache.org/jira/browse/CAMEL-5668 > > > What I am doing wrongs? Looks like soap faults are threated differently in > camel... > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Help-with-nmr-cxf-endpoints-and-fault-handling-tp5719720p5719859.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
