You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2006/03/07 08:33:53 UTC
[jira] Updated: (JCR-313) Allow to configure DB persistence
managers through JDNI
[ http://issues.apache.org/jira/browse/JCR-313?page=all ]
Jukka Zitting updated JCR-313:
------------------------------
Fix Version: 1.1
(was: 1.0)
> Allow to configure DB persistence managers through JDNI
> -------------------------------------------------------
>
> Key: JCR-313
> URL: http://issues.apache.org/jira/browse/JCR-313
> Project: Jackrabbit
> Type: Improvement
> Versions: 0.9
> Reporter: Martin Perez
> Assignee: Jukka Zitting
> Fix For: 1.1
> Attachments: dbpm-jndi.patch
>
> Currently, DB persistence managers have hardcoded urls. Even more, they will use a single connection with the drawbacks that this have regarding concurrency, performance and transactionality.
> It would be fairly better to allow to configure DB persistence managers through JDNI references to DataSource. So giving responsability to application server. Concurrency, performance and transactionability will be highly boosted with this approach.
> This could be a sample configuration :
> <PersistenceManager class="org.apache.jackrabbit.core.state.db.SimpleDbPersistenceManager">
> <param name="dataSource" value="jdbc/JackrabbitDS"/>
>
> .... think also about a way to pass params to data source, it should be simple ....
> <param name="schema" value="mysql"/>
> <param name="schemaObjectPrefix" value="${
> wsp.name}_"/>
> <param name="externalBLOBs" value="false"/>
> </PersistenceManager>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira