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] Commented: (JCR-1562) JNDI data sources with various PersistenceManager: wrong default values
Date Thu, 08 May 2008 13:00:55 GMT

    [ https://issues.apache.org/jira/browse/JCR-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595221#action_12595221
] 

Thomas Mueller commented on JCR-1562:
-------------------------------------

> Can you please advise an alternative
You could patch the classes yourself as long as there is no new version available. Otherwise
I don't have an alternative I am afraid.

> > For Oracle, a user name and password is required in any case.
> But it's provided by the datasource, 
> so it shouldn't be mandatory (or have a default value) at the PM's configuration level,
right ?

Yes. The Oracle JDBC driver requires user name and password. If that's configured in the data
source then that's OK.



> 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.


Mime
View raw message