[
https://issues.apache.org/jira/browse/TUSCANY-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464805
]
Amita Vadhavkar commented on TUSCANY-948:
-----------------------------------------
Jan15--rdb-das-jan15-jira-948-amita.jar,
sample-customer-j2se-das-jan15-jira-948-amita.zip,
rdb-das-jan15-jira-948-amita.txt
In this the change is making JNDI provider and Encryption Util pluggable
through a factory. So, we can support any available JNDI provider as well as
allow for
custom Encryption /Decryption of database password.
--in rdb-das--
Changed:
org.apache.tuscany.das.rdb.impl.DASImpl
config.xsd
New classes added:
org.apache.tuscany.das.rdb.util.JNDIContextProviderFactory
org.apache.tuscany.das.rdb.util.JNDIContextProviderInterface
org.apache.tuscany.das.rdb.util.SimpleSymmEncryption
org.apache.tuscany.das.rdb.util.SunJNDIProvider
org.apache.tuscany.das.rdb.util.SymmetricEncryptionUtilFactory
org.apache.tuscany.das.rdb.util.SymmetricEncryptionUtilInterface
--in sample-customer-j2se-das - to use the above changes
Changed:
Customers.xml
CustomerClient.java
> 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-Mx
> Reporter: Kevin Williams
> Fix For: Java-Mx
>
> Attachments: rdb-das-jan15-jira-948-amita.jar,
> rdb-das-jan15-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
>
>
> 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]
