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

Tom Jenkinson (JIRA) issues at jboss.org
Wed Mar 14 19:26:00 EDT 2018

     [ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson closed JBTM-3000.
    Resolution: Done

I think it would be better to create a thread in our forum over here: https://developer.jboss.org/en/jbosstm/content?filterID=contentstatus%5bpublished%5d~objecttype~objecttype%5bthread%5d

> 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

More information about the jbossts-issues mailing list