Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 36108 invoked from network); 18 Feb 2010 11:55:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Feb 2010 11:55:18 -0000 Received: (qmail 38866 invoked by uid 500); 18 Feb 2010 11:55:18 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 38790 invoked by uid 500); 18 Feb 2010 11:55:18 -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 38782 invoked by uid 99); 18 Feb 2010 11:55:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2010 11:55:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mrduguo@gmail.com designates 209.85.218.211 as permitted sender) Received: from [209.85.218.211] (HELO mail-bw0-f211.google.com) (209.85.218.211) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2010 11:55:10 +0000 Received: by bwz3 with SMTP id 3so44682bwz.9 for ; Thu, 18 Feb 2010 03:54:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=TJxrtqXPpWlUcW4EupHfdE+WC0eVO48IvumtpWZFBnc=; b=QQFbuIXpKwojREZiaItiQhHb877NSNspn73OyYKztaerIHvQplXp9w3DLFdmeZgHOt gHUqApMojWkCbXNef8Bj15yiAULnSfbVIi0vZtxarcXn5rPuHB/JlPN8qhlBccTsNAFi bUfm9B6K1OpoG5hUENH4Xk4sL/a1gYjJqyeZI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=sWC935SqPP1hqNsygoI58liRkbLEwYjtIhD1WIZwkqJ2Fs5YrVfNva2q8oByaaIi0l +JfJW7tqTgFEomUP2kxDH+bUYW8oDF81m8zx2XAGItcgL7nCnvVhIVT+4TgZ3WPliBHQ GLwuTjZDZTq9+iarY02Csirobwo3gpdastnuE= MIME-Version: 1.0 Received: by 10.204.33.148 with SMTP id h20mr2390852bkd.150.1266494088075; Thu, 18 Feb 2010 03:54:48 -0800 (PST) In-Reply-To: References: <510143ac1002170806n312514desd639aef826be0501@mail.gmail.com> <4B7CBC3B.7090803@gmail.com> Date: Thu, 18 Feb 2010 11:54:48 +0000 Message-ID: Subject: Re: [jr3] Plugin architecture From: Guo Du To: dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Feb 18, 2010 at 10:02 AM, Bertrand Delacretaz wrote: > Do you really think Jackrabbit should allow its core plugins to go > away at runtime? No, it's just one of OSGi feature doesn't need here. > i don't mind providing osgi support at a higher level, the core however > should IMO not have any osgi-dependenciesi. +1 I would prefer to have our core implementation based on bean style pojo class. Thus we can have xml, OSGi, war, spring or whatever container to assembly for final runtime. > First of all, I would define an API for configuration changes. This > API could be the regular JCR API, and the configuration could be > stored in special "system" nodes. There are two kind of configuration apart from user data:node definition and repository definition. It's good to store node definition inside the repository and api to manage changes. But the repository configuration shouldn't go inside repository. Think about store db connection username/password inside repository. > Extensibility of the importXML and exportDocumentView methods come to mind. It may worth to redefine how we import/export. Xml should just be one of format we support. I am not confident to use xml to export/import GB/TB size data. ContentHandler could responsible for how the data should be export/imported. -Guo