[ 
http://issues.apache.org/jira/browse/JCR-313?page=comments#action_12364958 ] 

Stefan Guggisberg commented on JCR-313:
---------------------------------------

the goals of the SimpleDbPersistenceManager implementation have been,
as its name suggests, being *simple*, having zero deployment requiremnts 
and minimal dependencies. it's predestined to be used with embedded 
databases such as e.g. Derby. 

the requested features would just add complexity, deployment overhead and no
real benefit  for the above use case and would defeat the original purpose of 
the
SimpleDbPersistenceManager.

i wouldn't be against a more elaborate JDBC based PM implementation that makes 
use of J2EE infrastructure features such as JNDI lookup of  the DataSource, etc.

> 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

Reply via email to