I've used recipient list a lot and it works quite well. Right now I'm using annotations for both REST and SOAP on the same interface and can thereby expose and route the values in the same fashion. You're right that there isn't a default but when you're using these there wouldn't really be a default anyway. Either the REST endpoint exists and thereby invokes your recipient list or it will be rejected by CXF as a non-existent resource before it ever gets to you anyway.
On Tue, Feb 9, 2016 at 5:11 PM, camel_case <cshoo...@remedypartners.com> wrote: > Yes, thanks, I was referring the interface, though I was using a resource > class instead with return nulls. > I think I now have a couple of options, I think I could also get the http > method from the exchange and pass to the recipient list, just as the > operationName is used though operationName gives finer grain control > perhaps. > Also it's possible to use choice, though I don't see the advantage over the > direct:$operationName call > except easier to have default route I guess. > > https://access.redhat.com/documentation/en-US/Fuse_ESB_Enterprise/7.1/html/Web_Services_and_Routing_with_Camel_CXF/files/Pojo-OpName.html > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Multiple-consumers-for-the-same-endpoint-is-not-allowed-cxfrs-vs-rest-dsl-tp5777492p5777498.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
