[
https://issues.apache.org/jira/browse/JCR-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557692#action_12557692
]
Marcel May commented on JCR-1305:
----------------------------------
Using JK in an app server environment with managed connections, I'm not sure
about how the app server will respond to getConnection(user,pwd).
The connection from the pool is already authenticated. Guess the app server
might not like it at all.
Has anyone tested JK+JNDI Bundle conf in any application server?
Can we get this fix into 1.4?
We've been really looking forward to JNDI support :-)
> JNDI data sources with BundleDbPersistenceManager:
> UnsupportedOperationException
> --------------------------------------------------------------------------------
>
> Key: JCR-1305
> URL: https://issues.apache.org/jira/browse/JCR-1305
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
>
> When using the org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory, the
> BundleDbPersistenceManager can not open a database connection via JNDI
> because the method DataSource.getConnection(user, password) is not supported.
> Instead, DataSource.getConnection() must be used for this to work.
> ConnectionFactory.getConnection should be changed to call this method if user
> name and password are empty.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
