Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A9623200BC0 for ; Mon, 31 Oct 2016 17:03:02 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A8189160AED; Mon, 31 Oct 2016 16:03:02 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 24379160B05 for ; Mon, 31 Oct 2016 17:03:01 +0100 (CET) Received: (qmail 23626 invoked by uid 500); 31 Oct 2016 16:03:01 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 23603 invoked by uid 99); 31 Oct 2016 16:03:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Oct 2016 16:03:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8767CCAD66 for ; Mon, 31 Oct 2016 16:03:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id h9LnX_1QOJYo for ; Mon, 31 Oct 2016 16:02:58 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1DB7E5F2F0 for ; Mon, 31 Oct 2016 16:02:58 +0000 (UTC) Received: from static.162.255.23.22.macminivault.com (unknown [162.255.23.22]) by mbob.nabble.com (Postfix) with ESMTP id 4E47834E4377 for ; Mon, 31 Oct 2016 08:54:00 -0700 (PDT) Date: Mon, 31 Oct 2016 09:02:04 -0700 (MST) From: DariusX To: users@camel.apache.org Message-ID: <1477929724320-5789523.post@n5.nabble.com> Subject: Camel-REST vs Cxfrs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Mon, 31 Oct 2016 16:03:02 -0000 I would like to expose some Camel routes via REST, and am considering using the REST DSL. (I do not have pre-existing REST-based web-service components.) Is there any reason/advantage to using camel-cxfrs or some other such component that supports REST in such a scenario? It appears to me that the Camel REST DSL is always the way to go unless one has legacy reasons to use something else, but I'd appreciate someone telling me if that's a wrong assumption. Also, is there a page somewhere on the Camel site that would speak to this: i.e. the motivation of using one over the other? thanks -- View this message in context: http://camel.465427.n5.nabble.com/Camel-REST-vs-Cxfrs-tp5789523.html Sent from the Camel - Users mailing list archive at Nabble.com.