[ http://issues.apache.org/jira/browse/JCR-313?page=comments#action_12366762 ]
Marcel Reutegger commented on JCR-313: -------------------------------------- What I was trying to say is: the current Simple DB PM uses prepared statements for all of the DB operations. Those prepared statements are kept for the full lifetime of the PM and only closed when the PM is shut down. A more general DB PM that uses a DataSource (pool) will not be able to use such long lived prepared statements. After a store operation it should close (return) the connection. Because the life time of a statement is bounded to the connection, the PM will have to close the statements as well and create new ones when the next store() occurs. > 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.0 > 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
