Hi, I don't know the JNDIDatabasePersistenceManager, but in Jackrabbit 1.4.1(I'm not sure when this will be released) will you can use the 'regular' bundle OraclePersistenceManager ( org.apache.jackrabbit.core.persistence.bundle.OraclePersistenceManager) with JNDI. See also: http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ
"As of Jackrabbit 1.4, the connection can be created using a JNDI Data Source as well. To do that, 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)" In Jackrabbit 1.4 there is a bug () so you need to specify the user name and password as well, but this might not work with your data source factory, see also: http://issues.apache.org/jira/browse/JCR-1305 Regards, Thomas > On Feb 11, 2008 4:03 PM, Rohnny Moland <[EMAIL PROTECTED]> wrote: > Hi, > > After upgrading to jackrabbit 1.4, we have some problems deploying on > oracle 10.1.3.3. We use the JNDIDatabasePersistenceManager, whch is > configured like this in repository.xml: > > <PersistenceManager > class=" > org.apache.jackrabbit.core.persistence.db.JNDIDatabasePersistenceManager"> > <param name="dataSourceLocation" > value="java:comp/env/jdbc/ourdatasource"/> > <param name="schemaObjectPrefix" value="${wsp.name}_"/> > <param name="schema" value="oracle"/> > <param name="externalBLOBs" value="false"/> > </PersistenceManager> > > Jackrabbit fails to instantiate this persistence manager. Is it a > configuration change in the JNDIDatabasePersistenceManager from > jackrabbit 1.3 to 1.4 which could be the problem? > > > Kind regards, > Rohnny >
