[ http://issues.apache.org/jira/browse/JCR-313?page=comments#action_12365006 ]
Jukka Zitting commented on JCR-313: ----------------------------------- Martin: > [OT]: Well, first of all, sorry if I offended someon putting the issue, > because it seems that I got hard responses. Don't be sorry. This is a valid and good idea that deserves to be thoroughly discussed. My undestanding is that the basic idea of Jackrabbit is that it is fully in control of the content a repository contains. Although the persistence model is highly configurable, the default Jackrabbit configuration has traditionally been to store data either directly in the filesystem or more recently to use an embedded database. The idea is that Jackrabbit provides a service that is at the same architectural level as a RDBMS (i.e. the backend), and that layering Jackrabbit on top of a separate backend system doesn't make much sense. The lack of advanced deployment options (storage clustering, etc.) and administrative tools make however the option of storing the actual data in a separate database server quite attractive. Jackrabbit should therefore offer first-class support for remote databases as well as embedded ones as persistence options. I can volunteer to take a deeper look at the required changes and whether separate embedded/external database persistence managers are needed. > 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 > > 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
