[
https://issues.apache.org/jira/browse/JCR-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594509#action_12594509
]
Thomas Mueller commented on JCR-1562:
-------------------------------------
> if (getSchema() == null) {
> setSchema("oracle");
> }
> shouldn't that be removed too?
No. The term 'schema' is a bit misleading: here the schema property controls
what .ddl file to use to create the tables. For Oracle, the file
src/main/resources/org/apache/jackrabbit/core/persistence/bundle/oracle.ddl
file is used. It doesn't have to do with the database schema.
See also http://issues.apache.org/jira/browse/JCR-1180
> JNDI data sources with various PersistenceManager: wrong default values
> -----------------------------------------------------------------------
>
> Key: JCR-1562
> URL: https://issues.apache.org/jira/browse/JCR-1562
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: core 1.4.2
> Reporter: Sven Rieckhoff
> Attachments: bundleDbNoDefaultUserPassword.txt
>
>
> With JCR-1305 Jackrabbit supports creating a connection throug a JNDI
> Datasource and without configuring user and password. This works for some but
> not all provided PersistenceManagers. Some of them - like the Oracle-specific
> BundleDBPersistenceManager - sets default values for user and password if
> none are provided in the jackrabbit config. This way its impossible to use
> such PersistenceManagers with the plain JNDI DS.
> This concerns the following BundleDbPersistenceManagers:
> OraclePersistenceManager, DerbyPersistenceManager, H2PersistenceManager.
> There also might be other PMs (perhaps some special
> SimpleDbPersistenceManagers) with similar behaviour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
