You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Shaun Barriball <sb...@yahoo.co.uk> on 2007/05/18 15:59:03 UTC
BundleDbPersistenceManager and JNDIDatabasePersistenceManager
Hi all,
I've read various posts about the performance benefits of using the new
Bundle persistence managers.
Ideally we'd like to externalise the database connection properties from the
repository.xml via a JNDI resource but can anyone confirm if it is possible
to a) use a JNDI database resource, and also b) leverage the benefits of
the bundle persistence managers?
Regards,
Shaun.
Re: JNDI and BundleDbPersistenceManager
Posted by Stefan Kurla <st...@gmail.com>.
Jukka, others.
Where can I find more information on the bundlePersistence managers? I
could not find it in the java docs....
On 5/24/07, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On 5/24/07, Shaun Barriball <sb...@yahoo.co.uk> wrote:
> > Am I correct to conclude - BundleDbPersistenceManagers are the recommended
> > configuration for Jackrabbit?
>
> Yes. Bundle persistence is not yet (as of Jackrabbit 1.3) the default
> configuration, mostly because we didn't have time to document it or
> create tools for migrating from previous persistence managers, but if
> you're starting a new repository then I would recommend using bundle
> persistence.
>
> > JNDI is not really recommended from a performance perspective even though
> > JNDI has the significant benefit of externalising the connection properties
> > to the application server.
>
> A JNDI configuration does not really affect performance in any
> significant way, but we tend to avoid such configurations since
> Jackrabbit doesn't really work like a typical JNDI DataSource client
> would. Instead of using a DataSource reference and acquiring a
> separate connection for each individual operation, the Jackrabbit
> database components typically use a single Connection for the entire
> lifetime of the repository. This doesn't work too well with connection
> pooling and other similar solutions people tend to associate with JNDI
> data sources.
>
> But if you just want to use JNDI to externalize the database
> configuration and understand the above-mentioned Jackrabbit usage
> pattern, then there is no downside to using JNDI.
>
> BR,
>
> Jukka Zitting
>
Re: JNDI and BundleDbPersistenceManager
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On 5/24/07, Shaun Barriball <sb...@yahoo.co.uk> wrote:
> Am I correct to conclude - BundleDbPersistenceManagers are the recommended
> configuration for Jackrabbit?
Yes. Bundle persistence is not yet (as of Jackrabbit 1.3) the default
configuration, mostly because we didn't have time to document it or
create tools for migrating from previous persistence managers, but if
you're starting a new repository then I would recommend using bundle
persistence.
> JNDI is not really recommended from a performance perspective even though
> JNDI has the significant benefit of externalising the connection properties
> to the application server.
A JNDI configuration does not really affect performance in any
significant way, but we tend to avoid such configurations since
Jackrabbit doesn't really work like a typical JNDI DataSource client
would. Instead of using a DataSource reference and acquiring a
separate connection for each individual operation, the Jackrabbit
database components typically use a single Connection for the entire
lifetime of the repository. This doesn't work too well with connection
pooling and other similar solutions people tend to associate with JNDI
data sources.
But if you just want to use JNDI to externalize the database
configuration and understand the above-mentioned Jackrabbit usage
pattern, then there is no downside to using JNDI.
BR,
Jukka Zitting
JNDI and BundleDbPersistenceManager
Posted by Shaun Barriball <sb...@yahoo.co.uk>.
Hi all,
Am I correct to conclude - BundleDbPersistenceManagers are the recommended
configuration for Jackrabbit?
JNDI is not really recommended from a performance perspective even though
JNDI has the significant benefit of externalising the connection properties
to the application server.
Thanks,
Shaun.
-----Original Message-----
From: Shaun Barriball [mailto:sbarriba@yahoo.co.uk]
Sent: 18 May 2007 14:59
To: users@jackrabbit.apache.org
Subject: BundleDbPersistenceManager and JNDIDatabasePersistenceManager
Hi all,
I've read various posts about the performance benefits of using the new
Bundle persistence managers.
Ideally we'd like to externalise the database connection properties from the
repository.xml via a JNDI resource but can anyone confirm if it is possible
to a) use a JNDI database resource, and also b) leverage the benefits of
the bundle persistence managers?
Regards,
Shaun.