Sergey, would you say that the current behavior is a bug in the cxfbean endpoint and at some point I will be able to remove my additional unmarshal/marshal route steps? Or is this how the endpoint should behave and all subsequent route steps must be able to deal with all supported client formats (@Produces)?
Thanks Ralf -----Original Message----- From: Ralf Steppacher <[email protected]> Reply-to: [email protected] To: [email protected] Subject: Re: RESTful route with Apache CXF Date: Mon, 10 Sep 2012 08:45:04 +0200 Well, I guess I could with a producer template. But routes using a producer template are not very "obvious" in the Spring XML and I try to avoid them. For now I worked around the problem by explicitly unmarshalling the PriceRequestMessage after the cxfbean route step and then marshalling it again at the very end of the route. Ralf -----Original Message----- From: Sergey Beryozkin <[email protected]> Reply-to: [email protected] To: [email protected] Subject: Re: RESTful route with Apache CXF Date: Fri, 07 Sep 2012 21:09:06 +0100 Can you do camel:enrich progarammatically, within getIndicativePrice(PriceRequestMessage prm) ? Cheers, Sergey
