On Mon, Mar 1, 2010 at 5:41 AM, Thomas Müller thomas.muel...@day.com 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
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
#
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 11:50, Thomas Müller thomas.muel...@day.com wrote:
String factoryClass = ...;
String url = ...?user=sapassword=xyz;
RepositoryFactory factory = (RepositoryFactory)
Class.forName(factoryClass).newInstance();
MapString, String parameters = new HashMapString, String();
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
On Mon, Mar 1, 2010 at 14:42, Thomas Müller thomas.muel...@day.com 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
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
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 the
