Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D194C1CC for ; Thu, 21 Jun 2012 01:05:11 +0000 (UTC) Received: (qmail 29967 invoked by uid 500); 21 Jun 2012 01:05:11 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 29933 invoked by uid 500); 21 Jun 2012 01:05:10 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 29920 invoked by uid 99); 21 Jun 2012 01:05:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 01:05:10 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com designates 209.85.160.45 as permitted sender) Received: from [209.85.160.45] (HELO mail-pb0-f45.google.com) (209.85.160.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 01:05:04 +0000 Received: by pbbro12 with SMTP id ro12so1501758pbb.32 for ; Wed, 20 Jun 2012 18:04:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+cYq5twq1b++GywKAanrVKe7hOCECR8N11CN6DVVZG0=; b=A8giUuoMX7De5jdQiOquTOP3tIcRCnkuhbrBpX+UBQLn7ZrLbfMDe1/QOBVzfo5Dxu oYySQbIel2H4xf1dUuNRhr/oQiLZRrYzBjV25XW9MS8p0Q+aJqpoDDbh7jr3Ir3c2+fQ 1EkZD4UU6bA/T/fcOoLS2q+m/6mAIQgi6oEip/53klqMI/tNZn0eIqWv8ARYXSjvEYNK v5kLZ2kOoYRwPecvMfadvYU4xyK07HU+r+O8rjv85Zch9FkJ1K7cIF9wQI9PKyrVc20D gARRT7UgvY9gwzf6/HXvmXxEIRqMTO1FCdZj10fVgnS4FJIz1TCOLfK+tRuLS7LcJa6i kOUA== Received: by 10.68.238.166 with SMTP id vl6mr61365851pbc.96.1340240682930; Wed, 20 Jun 2012 18:04:42 -0700 (PDT) Received: from [192.168.0.158] ([123.116.40.37]) by mx.google.com with ESMTPS id gg10sm12770474pbc.51.2012.06.20.18.04.36 (version=SSLv3 cipher=OTHER); Wed, 20 Jun 2012 18:04:41 -0700 (PDT) Message-ID: <4FE2731C.3030708@gmail.com> Date: Thu, 21 Jun 2012 09:04:28 +0800 From: Willem Jiang User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: dev@camel.apache.org Subject: Re: [DISCUSSION] Camel on Android? References: <4FE1C23C.1090508@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Yeah, it's a interesting topic. I know lots of third part libs which camel use are support Android. As Camel can run without Spring, I think we will not do much work to let the core run within Android. On Wed Jun 20 22:41:36 2012, Henryk Konsek wrote: >> I don't think there's much we can do for >> camel 2.x, but it is one of my secret goals to have a camel-3.0 that runs >> embedded. I hope we'll talk more about this in the coming months. > > I think it's pretty interesting topic. Maybe we could create wiki page > where we will gather the current status of making Camel > Android-runnable? At the beginning we could note there what are the > problems with Camel on Android. Then we could think about possible > solutions. > > I was tempted to look closer at this topic, but I don't want to > reinvent the wheel :) . > -- Willem ---------------------------------- FuseSource Web: http://www.fusesource.com Blog: http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang Weibo: willemjiang