Changes in DAS Config to support authenticated connection using data source
---------------------------------------------------------------------------
Key: TUSCANY-1698
URL: https://issues.apache.org/jira/browse/TUSCANY-1698
Project: Tuscany
Issue Type: Improvement
Components: Java DAS RDB
Affects Versions: Java-DAS-Next
Reporter: Amita Vadhavkar
Assignee: Amita Vadhavkar
Fix For: Java-DAS-Next
in RDB-DAS, when we use external DataSource, we do not pass userName,
password. But MySQL (which with InnoDB supports Txn and works well with JOTM)
does need id, pwd in ds.getConnection(). This can be case with other DBs as
well.
So, it looks like DAS config.xsd needs to allow passing userName, password in
ConnectionInfo too ( and not just for ConnectionProperties).
Thus below will be the changed DAS config portion:-
<xsd:complexType name="ConnectionInfo">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="ConnectionProperties"
type="config:ConnectionProperties"/>
</xsd:sequence>
<xsd:attribute name="dataSource" type="xsd:string"/>
<xsd:attribute name="managedtx" type="xsd:boolean" default="true"/>
<xsd:attribute name="userName" type="xsd:string" default=""/>
<xsd:attribute name="password" type="xsd:string" default=""/>
</xsd:complexType>
<xsd:complexType name="ConnectionProperties">
<xsd:attribute name="driverClass" type="xsd:string"/>
<xsd:attribute name="databaseURL" type="xsd:string"/>
<xsd:attribute name="loginTimeout" type="xsd:int" default="0"/>
</xsd:complexType>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
