Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BAB5A10F35 for ; Tue, 9 Jul 2013 21:02:47 +0000 (UTC) Received: (qmail 68977 invoked by uid 500); 9 Jul 2013 21:02:47 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 68941 invoked by uid 500); 9 Jul 2013 21:02:47 -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 68933 invoked by uid 99); 9 Jul 2013 21:02:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 21:02:47 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: encountered temporary error during SPF processing of domain of henry.werner@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 21:02:42 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Uwf2w-000175-7g for users@camel.apache.org; Tue, 09 Jul 2013 14:02:02 -0700 Date: Tue, 9 Jul 2013 14:02:02 -0700 (PDT) From: hwerner To: users@camel.apache.org Message-ID: <1373403721907-5735379.post@n5.nabble.com> Subject: twitter version updated to v1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I'm trying to use twitter in my routes and am currently getting the 410 error message from twitter stating that twitter REST api v1.0 is no longer being used, please update to v1.1. Does this mean Camel needs to update, or do I need to update my api somewhere? This is for a basic twitter search call, and as such we don't really have an api for it, we are simply utilizing camel's twitter component. So, ultimately, I would like to know whether we, now, need to register an app, or if camel just needs to update their component to utilize twitter v1.1, and if camel has, is the spring dsl uri call for a search different? -- View this message in context: http://camel.465427.n5.nabble.com/twitter-version-updated-to-v1-1-tp5735379.html Sent from the Camel - Users mailing list archive at Nabble.com.