Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 42244 invoked from network); 21 Sep 2006 21:12:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Sep 2006 21:12:45 -0000 Received: (qmail 88356 invoked by uid 500); 21 Sep 2006 21:12:43 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 88331 invoked by uid 500); 21 Sep 2006 21:12:43 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 88322 invoked by uid 99); 21 Sep 2006 21:12:43 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Sep 2006 14:12:43 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=jukka.zitting@gmail.com; domainkeys=good Authentication-Results: idunn.apache.osuosl.org smtp.mail=jukka.zitting@gmail.com; spf=pass X-ASF-Spam-Status: No, hits=0.5 required=5.0 tests=DNS_FROM_RFC_ABUSE Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates 64.233.184.235 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [64.233.184.235] ([64.233.184.235:40482] helo=wr-out-0506.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id EC/25-03726-84003154 for ; Thu, 21 Sep 2006 14:12:40 -0700 Received: by wr-out-0506.google.com with SMTP id i23so447899wra for ; Thu, 21 Sep 2006 14:12:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ki3agduENj7IA6PC92c45rmH+yBamqlMRenShuLu4ocWlsSfo1YRwXrGYA3Vleb6sUAWfpcAeSxKiNOg+y3fR6CrdvMdkn7OQxol0sk4XR7fcpLU3UpvjKYP38Y5Ac1ij3NhrHMLooZ9CUdcsyMhFfyzlqSegDCCnk99ibLGaVQ= Received: by 10.90.66.9 with SMTP id o9mr5438000aga; Thu, 21 Sep 2006 14:12:37 -0700 (PDT) Received: by 10.90.97.2 with HTTP; Thu, 21 Sep 2006 14:12:37 -0700 (PDT) Message-ID: <510143ac0609211412k530c0b2dyb86a12e3fbac5013@mail.gmail.com> Date: Fri, 22 Sep 2006 00:12:37 +0300 From: "Jukka Zitting" To: dev@jackrabbit.apache.org Subject: Re: [Jackrabbit Wiki] Update of "JcrLinks" by DavidNuescheler In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060921123956.24693.71567@ajax.apache.org> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 9/21/06, David Kennedy wrote: > The description of the page is "This page contains links to articles and > applications based on JCR and Jackrabbit." > > How is the distinction made between those applications based on JSR 170 > only and those based on Jackrabbit (and thus JSR 170 as well)? The "and" in the sentence was meant as "articles and applications based on JCR *and* articles and applications based on Jackrabbit" instead of "articles and applications based on *both* JCR and Jackrabbit". Feel free to modify the page to make the classification clearer, though in general I don't think we should have too many applications that depend directly on Jackrabbit core instead of the JCR API. BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - info@yukatan.fi Software craftsmanship, JCR consulting, and Java development