A fix has been submitted to the trunk. https://issues.apache.org/activemq/browse/CAMEL-1774
Thanks, William On Mon, Jun 29, 2009 at 8:12 PM, William Tam<[email protected]> wrote: > It sounds like a bug. I'll take a look. Thanks. > > On Mon, Jun 29, 2009 at 2:33 PM, Srivatsa Katta<[email protected]> wrote: >> >> Hi, >> >> Am having a jetty endpoint which has been backed by the CXF bean processor, >> am using jax-rs compatible cxfbean component. It absolutely works fine in >> happy path scenarios, but if I have to return the custom cxf Response by >> setting the http status code explicitly the same response is not propagated >> back by to the client. >> >> For Eg: >> >> If I have a POST method in CXF service, on successful execution of POST >> method (lets say creation of entity), I return a custom cxf Response object >> (which is a generic pattern used in CXF afaik) by setting http status code >> to 301. The same http status code is not returned to the camel client. >> >> Am wondering if this is a standard procedure used while using cxf beans, if >> it is then why is camel not propagating the same to the client ? If its not >> the standard practice to return custom response from cxf beans how does the >> client knows if the POST method is successful or not ? how do we return >> custom http status codes instead of returning 200 in case of success and 500 >> in case of error/exception (which is what camel returns by default) >> >> Any help regarding this is appreciated.. >> >> PS: Am using Camel 2.0 M2 release. >> >> Cheers!! >> Katta >> -- >> View this message in context: >> http://www.nabble.com/Response-propogation-from-cxfbean-tp24259344p24259344.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> >
