jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-948) Support for JNDI configuration of BundleDbPersistenceManager
Date Wed, 28 Nov 2007 14:45:43 GMT

     [ https://issues.apache.org/jira/browse/JCR-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Mueller updated JCR-948:
-------------------------------

    Attachment: jndi.patch

My patch solves the problem not only for BundleDbPersistenceManager, but also for the DbDataStore.
I suggest to use the same mechanism for all modules that require a connection.

In this patch, no new property is required, instead the existing driver and url properties
are used: To use JNDI, the driver class name must reference a javax.naming.Context class (for
example javax.naming.InitialContext), and the URL must be the JNDI URL (for example java:comp/env/jdbc/Test).

If nobody objects, I will check in this patch in a few days.

> Support for JNDI configuration of BundleDbPersistenceManager
> ------------------------------------------------------------
>
>                 Key: JCR-948
>                 URL: https://issues.apache.org/jira/browse/JCR-948
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Miguel Angel Jiménez Sampedro
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: JCR-948-patch.txt, jndi.patch
>
>
> It would be nice to have the option to configure BundleDbPersistenceManager database
specifying a JNDI name of a DataSource.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message