[
https://issues.apache.org/jira/browse/TUSCANY-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462453
]
Amita Vadhavkar commented on TUSCANY-948:
-----------------------------------------
Note:
** New elements and attributes in config.xsd are optional, old das config xmls
will work as is. Tested companyweb
** Sample Question: how to create db if does not exist - for db2. This is
implemented in sample for mysql
and derby
** RDB DAS Question: Also, when the JNDI datasource is defined through Tomcat
or another
J2EE env. it is possible to configure different properties for same and not
just mandatory ones.
Shall the same approach be followed, in which case ConnectionProperties will
have place for all
the mandatory + optional properties. Or shall we just provide support for
defining the
mandatory properties?
**Used symmetric encryption for password- using DES/ECB/PKCS5Padding Cipher
instance type.
**Current code is dynamic to take care of different set of connection
properties. User should
provide only supported (by the current data source) attributes in the config.
rdb-das will
invoke only methods for same to set the data in the data source of interest.
**Files changed - find comment in the code //JIRA-948 to check for code changes
**********SAMPLE********************************************************************
sample zip: sample-customer-j2se-das-jan5-amita.zip
1)new sample - sample-customer-j2se-das
This sample creates database if not present and sets necessary tables,
procedures, data etc.
(create database happens for MySQL and Derby, not DB2).
It then invokes DAS commands for CRUD on the given database. New config
attributes for
J2SE env. DataSource support are used in the config xml.
*****************RDB-DAS*************************************************************************
svn patch file :- rdb-das-jan5-jira-948-amita.txt And code
zip:rdb-das-jan5-jira-948-amita.zip
patch
2)org.apache.tuscany.das.rdb.config.wrapper.MappingWrapper.addConnectionInfo
patch 3)org.apache.tuscany.das.rdb.ConfigHelper.addConnectionInfo()
patch 4)config.xsd
patch 5)org.apache.tuscany.das.rdb.impl.DASImpl
zip 6)org.apache.tuscany.das.rdb.util.SymmetricEncryptionUtil - New
patch 7)org.apache.tuscany.das.rdb.impl.ConnectionImpl.prepareStatement - if
useGetGeneratedKeys
zip 8)org.apache.tuscany.das.rdb.exception.DataSourceInitializationException
- New
zip 9)2 jars of easymock in classpath
patch 10)pom.xml - dependecy for easymock
> 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-jan5-jira-948-amita.txt,
> rdb-das-jan5-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]
