[
https://issues.apache.org/jira/browse/TUSCANY-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465996
]
Amita Vadhavkar commented on TUSCANY-948:
-----------------------------------------
Jan 18:
Modifications:
config.xsd changed to separate non DataSource related
attributes from Data Source related attributes.
Below is from config.xsd
<xsd:complexType name="HelperProperties">
<xsd:attribute name="dataSourceClass" type="xsd:string"/>
<xsd:attribute name="JNDIProvider" type="xsd:string" default="sun"/>
<xsd:attribute name="EncryptionUtil" type="xsd:string"
default="SimpleSymmEncryption"/>
</xsd:complexType>
<xsd:complexType name="ConnectionProperties">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="HelperProperties"
type="config:HelperProperties"/>
</xsd:sequence>
<xsd:attribute name="user" type="xsd:string"/>
<xsd:attribute name="password" type="xsd:string"/>
<xsd:attribute name="key" type="xsd:string"
default="193-155-248-97-234-56-100-241"/>
<xsd:attribute name="databaseName" type="xsd:string"/>
<xsd:attribute name="charset" type="xsd:string"/>
<xsd:attribute name="loginTimeout" type="xsd:int"/>
</xsd:complexType>
<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="contextAvailable" type="xsd:boolean" default="true"/>
</xsd:complexType>
Patch and sample - contain the necessary changes for the above cfg changes -
1)sample-customer-j2se-das-jira-948-jan18-amita.jar, 2)
rdb-das-jan18-jira-948-amita.txt
> Consider DAS config connection info for J2SE environment
> --------------------------------------------------------
>
> Key: TUSCANY-948
> URL: https://issues.apache.org/jira/browse/TUSCANY-948
> Project: Tuscany
> Issue Type: Improvement
> Components: Java DAS RDB
> Affects Versions: Java-SCA-Mx
> Reporter: Kevin Williams
> Fix For: Java-DAS-Mx
>
> Attachments: rdb-das-jan15-jira-948-amita.jar,
> rdb-das-jan15-jira-948-amita.txt, rdb-das-jan18-jira-948-amita.txt,
> rdb-das-jan5-jira-948-amita.txt, rdb-das-jan5-jira-948-amita.zip,
> sample-customer-j2se-das-jan15-jira-948-amita.zip,
> sample-customer-j2se-das-jan5-jira-948-amita.zip,
> sample-customer-j2se-das-jira-948-jan18-amita.jar
>
>
> Currently the DAS allow users to specfify a JDBC Connection for the DAS to
> utilize by either providing a JDBC Connection explicitly or provifing a JNDI
> name in the config file. We should reconsider allowing DriverManager info
> to be provided to allow similar, config-based set up, in a J2SE enviroinment.
> I know this was debated in the past but I cannot recall if this was deferred
> or rejected. The issues may have been around the need to include
> user/password info in the DriverManager info.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
