Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 82295 invoked from network); 25 Jul 2007 10:09:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jul 2007 10:09:02 -0000 Received: (qmail 21270 invoked by uid 500); 25 Jul 2007 10:09:03 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 20896 invoked by uid 500); 25 Jul 2007 10:09:01 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 20887 invoked by uid 99); 25 Jul 2007 10:09:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jul 2007 03:09:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of stefan.guggisberg@gmail.com designates 209.85.128.185 as permitted sender) Received: from [209.85.128.185] (HELO fk-out-0910.google.com) (209.85.128.185) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jul 2007 03:09:00 -0700 Received: by fk-out-0910.google.com with SMTP id b27so14634fka for ; Wed, 25 Jul 2007 03:08:38 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ukh35nXA8s0D2OZTD+++fz/GWqN7Xoht5i5Q0ebPXhjL7MmNaV6WRvqXgk6hgg1wijQkQVEbKW+48oSV72E8DZKipbo5u7pxSynsjVfyVgb5uvpEAz78KqYTblsbAm6pyTTR28vG+5PbGxed1B4wMEE8mVHkO66VrYj+KpFMqgY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=K7sYatzMYwAyLJ8TQPlrfeSD7zvFSsCIQXpZ6ZHRrSmqd/xd9rCdQnFYsD5NBsGPQOP7j/dDvL6sbzcMNhTCTPgI32X534zGWYXUvzBqOOsXNMyc72zK1tO3pc+hcf6+uyJnw9JrFoxHM70yTRHFvIxXV8O6buLLpSMPfO3ZfRQ= Received: by 10.82.105.13 with SMTP id d13mr223823buc.1185358118498; Wed, 25 Jul 2007 03:08:38 -0700 (PDT) Received: by 10.82.171.9 with HTTP; Wed, 25 Jul 2007 03:08:38 -0700 (PDT) Message-ID: <90a8d1c00707250308n2dbf7131q94be17264eff76d6@mail.gmail.com> Date: Wed, 25 Jul 2007 12:08:38 +0200 From: "Stefan Guggisberg" To: users@jackrabbit.apache.org Subject: Re: File-based configuration for BindableRepository too restrictive In-Reply-To: <46A602CE.40807@modularity.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46A602CE.40807@modularity.net.au> X-Virus-Checked: Checked by ClamAV on apache.org hi ben On 7/24/07, Ben Fortuna wrote: > Hi all, > > Are there plans to offer alternate means for loading repository > configuration when using RegistryHelper/BindableRepository? Requiring > a file-based configuration seems way too restrictive to me - > especially when RepositoryConfig supports loading via InputStream. It while it would certainly be possible it wouldn't be just a matter of adding a couple of additional method signatures. note that since BindableRepository needs to implement javax.naming.Referenceable you'd need to serialize the config file anyway somehow. for more (implementation) details please take a look at BindableRepository#getReference() and BindableRepositoryFactory#getObjectInstance(). > also makes it difficult to use in an OSGi environment. > > If you want me to write a patch let me know. patches are always welcome :-) please create a jira improvement issue and attach the patch. thanks stefan > > regards, > ben >