You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2006/03/17 11:30:00 UTC
[jira] Assigned: (JCR-355) Extract JDBC Connection Init
[ http://issues.apache.org/jira/browse/JCR-355?page=all ]
Stefan Guggisberg reassigned JCR-355:
-------------------------------------
Assign To: Stefan Guggisberg
> Extract JDBC Connection Init
> ----------------------------
>
> Key: JCR-355
> URL: http://issues.apache.org/jira/browse/JCR-355
> Project: Jackrabbit
> Type: Improvement
> Components: core
> Versions: 0.9, 1.1, 1.0.1, 1.0
> Reporter: Michael Young
> Assignee: Stefan Guggisberg
> Priority: Minor
>
> An intermediate step to allowing a PM to be easily configurable through JNDI would be to extract the connection init. This will allow system integrators to subclass/wrap and dynamically configure a customized Simple PM. In org.apache.jackrabbit.core.state.db.SimpleDbPersistenceManager:
> Replace lines (296-298) with
> initConnection();
> Add:
> /**
> * Initialize the JDBC connection
> **/
> protected void initConnection() throws Exception {
> Class.forName(driver);
> con = DriverManager.getConnection(url, user, password);
> con.setAutoCommit(false);
> }
--
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