I supposed that's a matter of preference. I've used CXF in blueprint and am very comfortable with it. I'll usually us a single bundle and commonly setup up both SOAP and REST endpoints in there using annotated interfaces. Then I'll use the operationName in a recipient list to route the requests to the same bundle, whether SOAP or REST, and then deal with the logic in there and return results.
I like that because it puts the set up of all security, REST/SOAP, etc. in one place. The data model/bean is then routed into Camel and that point I'm free of any REST/SOAP concerns. But I may like that simply because I've never used the REST DSL and don't anticipate any immediate need for it. On Tue, Nov 1, 2016 at 7:51 AM, DariusX <dariuscoo...@gmail.com> wrote: > Claus Ibsen-2 wrote > > Camel in Action 2nd ed book has a full chapter on REST and various ways > to > > use it with Camel. > > Yes, looking at the MEAP edition got me wondering if that was the general > direction: i.e. to encourage the use of the REST DSL unless there were > specific reasons for one of the other approaches. > > Thank you both for your answers; very informative. > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Camel-REST-vs-Cxfrs-tp5789523p5789571.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
