On Mon, Mar 1, 2010 at 14:42, Thomas Müller wrote:
>> Couldn't this be done by a special wrapping Repository implementation?
>
> That's problematic. Such a wrapper would have quite some overhead. The
> JCR API is not easily "wrapable" if you want to do it correctly: you
> would have to wrap almost
Hi,
Currently Jackrabbit doesn't support relayed initialization. Unless I
misunderstood Felix, he would also like to get rid of this
restriction.
Just to clarify: my suggestion is *not* about requiring the repository
is initialized when the first session is opened. It's also *not* about
requiring
On Mon, Mar 1, 2010 at 11:50, Thomas Müller wrote:
> String factoryClass = "...";
> String url = "...?user=sa&password=xyz";
> RepositoryFactory factory = (RepositoryFactory)
> Class.forName(factoryClass).newInstance();
> Map parameters = new HashMap();
> parameters.put("url", url);
> Repository r
Hi,
-1 on defining this on this isolated level.
This should be part of a broader concept of how to architect/structure
JR3 and its backend connections.
Regards
Felix
On 28.02.2010 16:40, Thomas Müller wrote:
> Currently Jackrabbit initializes the repository storage (persistence
> manager) when
On Mon, Mar 1, 2010 at 10:50 AM, Thomas Müller wrote:
> Currently, Jackrabbit requires to be able to create a database
> connection when initializing.
I was thought like this too :)
> It depends on what you mean with "repository level". It doesn't make
> sense to store the user name and password
Hi,
> I am not clear what credentials you are refering to
I refer to the database user name and password that are currently
stored in the repository.xml (except when using JNDI):
http://jackrabbit.apache.org/api/1.5/org/apache/jackrabbit/core/persistence/bundle/BundleDbPersistenceManager.html
#
On Mon, Mar 1, 2010 at 5:41 AM, Thomas Müller wrote:
> The question is: should Jackrabbit 3 *require* (like now) that the
> credentials for the storage are included in the repository
> configuration? I think for some storage backends it should not require
> that. Instead (only in those cases), it
Hi,
> I would prefer to initialise the repository at first place and make sure
> everything
> is correctly for repository
I wrote: *allow* delayed initialization (allow, not require).
> If user want delay the initialisation, may create the repository
> reference only when first accessed.
If th
On Sun, Feb 28, 2010 at 3:40 PM, Thomas Müller wrote:
> I suggest to allow delayed initialization (allow, not require). For
> some storage backends, the repository could initialize when opening
> the first session.
-1
Repository/storage is critical for most of application, I would prefer
to init
Currently Jackrabbit initializes the repository storage (persistence
manager) when creating the repository object. If the repository data
is stored in relational database, then the database connection is
opened at that time.
I suggest to allow delayed initialization (allow, not require). For
some
10 matches
Mail list logo
