[jbossts-issues] [JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections

[Daniel Shaver (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545399#comment-13545399 ] 

Daniel Shaver commented on JBTM-3000:
-------------------------------------

Nevermind, it looks like the null username and password issue was resolved in 5.8.0 (I was using 5.5.3 originally) inside BaseTransactionalDriverXAConnection:

{code:java}
            if ((_user == null || _user.isEmpty()) && (_passwd == null || _passwd.isEmpty())) {
                if (jdbcLogger.logger.isTraceEnabled()) {
                    jdbcLogger.logger.trace("BaseTransactionalDriverXAConnection - getting connection with no user");
                }

                _theConnection = _theDataSource.getXAConnection();
            } else {
                if (jdbcLogger.logger.isTraceEnabled()) {
                    jdbcLogger.logger.trace("BaseTransactionalDriverXAConnection - getting connection for user " + _user);
                }

                _theConnection = _theDataSource.getXAConnection(_user, _passwd);
            }
{code}

But I'm still seeing issues. Requires further digging.

> Support for Oracle Wallet JDBC connections
> ------------------------------------------
>
>                 Key: JBTM-3000
>                 URL: https://issues.jboss.org/browse/JBTM-3000
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>            Reporter: Daniel Shaver
>            Priority: Optional
>
> In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet.
> This means that Narayana does not support Oracle Wallet JDBC connections.
> This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. 
> {code:java}
>             user = info.getProperty(TransactionalDriver.userName, "");
>             passwd = info.getProperty(TransactionalDriver.password, "");
> {code} 
> and in com.arjuna.ats.internal.jdbc.ConnectionManager
> {code:java}
>         String user = info.getProperty(TransactionalDriver.userName, "");
>         String passwd = info.getProperty(TransactionalDriver.password, "");
> {code}
> I believe it should be okay to just remove default value so that the client's input is always taken as-is?



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)