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 6F0C49E22 for ; Tue, 20 Mar 2012 08:09:21 +0000 (UTC) Received: (qmail 4787 invoked by uid 500); 20 Mar 2012 08:09:21 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 4726 invoked by uid 500); 20 Mar 2012 08:09:20 -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 4714 invoked by uid 99); 20 Mar 2012 08:09:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Mar 2012 08:09:20 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com designates 209.85.210.173 as permitted sender) Received: from [209.85.210.173] (HELO mail-iy0-f173.google.com) (209.85.210.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Mar 2012 08:09:13 +0000 Received: by iafj26 with SMTP id j26so13505566iaf.32 for ; Tue, 20 Mar 2012 01:08:53 -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=hef11oBznW69M3N7R9D/vOb/xdu2nmAC3/trPeKbcN4=; b=0ZV5nZwDnMPN59xxVcB62HcSsKQkqwNbmyUQTfvB3Gmhux5CswGXRmCkk08vLWedaf LNn27OzL6l4wF7T6nJySVlJuqf4xSw+1Jbb5udsKX2q76adTd2tjnrw/S+n0wGYpBQeP IRWmalDcshUz6LwPImAZiJeKxtUN8yYM66yhUZqi5m4zStCWqK0XqppRRe2pgqSL+4Ot YCRfh2Xv7pDSdvnqQUMtI6MRntWw99UUAkguHwxpb0Ema1oFQHsr54Rrf2NEsC4D2Cmr C57ETCMDeOsd2jjTjj2aZaaicrkZzMMhPZFwwl7T/mNar3DTG7MCBQ+8JoYKeLp8cWji xcZQ== Received: by 10.43.118.134 with SMTP id fq6mr5150267icc.41.1332230933044; Tue, 20 Mar 2012 01:08:53 -0700 (PDT) Received: from [192.168.0.158] ([123.116.39.138]) by mx.google.com with ESMTPS id hq3sm20581969igc.0.2012.03.20.01.08.42 (version=SSLv3 cipher=OTHER); Tue, 20 Mar 2012 01:08:51 -0700 (PDT) Message-ID: <4F683B08.5050102@gmail.com> Date: Tue, 20 Mar 2012 16:08:40 +0800 From: Willem Jiang User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: dev@camel.apache.org Subject: Re: [DISCUSS] Camel and MongoDB References: <1331294796600-5550388.post@n5.nabble.com> <1630276.7ZcoyC4xga@dilbert.dankulp.com> In-Reply-To: <1630276.7ZcoyC4xga@dilbert.dankulp.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org BTW, there are also some tests in the other camel component which dependents on other online service are not enable by default. Such as camel-twitter, camel-xmpp. If the user wants to run the test himself, he could enable the test by setting up the accounts and using a special maven profile. On Tue Mar 20 01:22:10 2012, Daniel Kulp wrote: > On Monday, March 19, 2012 04:43:02 PM Raul Kripalani wrote: >> Hi Ashwin! >> >> I looked into that but the cost of mocking out the MongoDB driver is high. >> Write operations on MongoDB are essentially asynchronous and there is >> additional complexity involved in the process to mock out the entire >> thing. Weighing pros and cons, my conclusion is that the effort simply >> doesn't pay off. >> >> Not only the upfront effort of mocking is high, but the cost of upgrading >> the component to work with newer versions of the MongoDB driver would >> increase too. Truth be told, the ideal solution would be mocking just the >> database and not the driver, but entails simulating low-level TCP packets, >> and that is definitely off the table I guess. >> >> Just to clarify, the MongoDB Java driver is Apache-licensed. While the >> database itself is licensed under GNU AGPL 3.0, the Apache infrastructure >> would not be hosting a MongoDB instance at all. So would there be any >> conflict in hitting the public cloud with our tests? > > As long as those tests are NOT enabled by default and those tests do not > require any specific user credentials or similar that people are required to > apply for, then it's probably not a huge deal. > > Dan > > > >> >> Regards, >> * * >> *Raúl Kripalani >> Principal Consultant | FuseSource Corp. >> raul@fusesource.com | fusesource.com >> mobile: +34 607 04 04 54 >> skype: raul.fuse | twitter: @raulvk, >> @fusenews >> * >> >> >> >> On 9 March 2012 12:06, Ashwin Karpe wrote: >>> Hi Raul, >>> >>> I ran into a similar issue when I developed the Camel SIP component and >>> was not in a position to include a SIP provider due to the fact that >>> there were no Apache friendly licensed providers available. >>> >>> In order to test, I created a stripped down, mock, SIP server that >>> mimicked the key capabilities of the real thing and used it for my >>> testing as well as >>> something that could be used in absence of a real SIP server. >>> >>> Doing something like that will avoid this hosting problem since there >>> are >>> some GPL license issues involved as well... Can you please check the >>> camel-sip component and see if you could do something like that... >>> >>> Cheers, >>> >>> Ashwin... >>> >>> >>> ----- >>> --------------------------------------------------------- >>> Ashwin Karpe >>> Apache Camel Committer& Sr Principal Consultant >>> FUSESource (a Progress Software Corporation subsidiary) >>> http://fusesource.com >>> >>> Blog: http://opensourceknowledge.blogspot.com >>> --------------------------------------------------------- >>> -- >>> View this message in context: >>> http://camel.465427.n5.nabble.com/DISCUSS-Camel-and-MongoDB-tp5117168p55 >>> 50388.html Sent from the Camel Development mailing list archive at >>> Nabble.com. -- Willem ---------------------------------- FuseSource Web: http://www.fusesource.com Blog: http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang Weibo: willemjiang