Re: [DAS]Approach for JIRA-948

Hi All, Please see the latest patch on Jan 18 and associated Note and give your comments about changes, corrections etc. Regards, Amita On 1/10/07, Amita Vadhavkar [EMAIL PROTECTED] wrote: Hi, Regarding the ecryption util, am trying for a clean new util. For JNDI context provider - used

Re: [DAS]Approach for JIRA-948

Hi, Regarding the ecryption util, am trying for a clean new util. For JNDI context provider - used EasyMock as a sample. It can be replaced by sun's fscontext or jboss's jnp. Jboss mentions its free use. Please let me know if there can be any licensing implications in using sun or jboss. Also,

Re: [DAS]Approach for JIRA-948

Amita wrote : Also, a few questions on the same line, do we specify some restrictions in any doc about the driver compliance to any particular jdbc standard like jdbc 3.0etc.? I'll do some research on this... And, now with this JIRA - I just want to confirm that, it is responsibility of the

Re: [DAS]Approach for JIRA-948

Hi Amita I got curious about the changes inside ConnectionImpl. Looks like you have introduced a error handling inside the ConnectionImpl.prepareStatementwhere you try to prepare the statement with the option to return generated keys, but if an abstract method error is found, you then resubmit

Re: [DAS]Approach for JIRA-948

Hi Amita Another question I have is regarding EasyMock dependency, looks like you are using the in DASImpl to create a context ? Or is that a piece of test that got left inside DASImpl by mistake ? -- Luciano Resende http://people.apache.org/~lresende On 1/8/07, Luciano Resende [EMAIL

Re: [DAS]Approach for JIRA-948

One more, related to Licensing. In your patch, SymetricEncryptionUtil.java source is basically a copy from the WebSite http://www.informit.com/guides/content.asp?g=javaseqNum=31rl=1 Looking at the website legal information http://www.informit.com/about/legal.asp?rl=1, the rights of the code

Re: [DAS]Approach for JIRA-948

Hi Luciano, Yes, it was for DB2 driver db2java.jar - the file bldlevel in this jar specifies the version as D:/wsdb/db2nt_v81ga/s021011. This jar comes with DB2 8.1.0.24. It does not support the syntax connection.prepareStatement(String, int). Also, a few questions on the same line, do we

Re: [DAS]Approach for JIRA-948

Hi, Have got the code changes working for Derby and testing for DB2 and MySQL. config.xsd will have xsd:complexType name=ConnectionInfo xsd:sequence xsd:element maxOccurs=1 minOccurs=0 name=ConnectionProperties type=config:ConnectionProperties/ /xsd:sequence

Re: [DAS]Approach for JIRA-948

Thank you Brent. I will work on all the below suggestions. Some more questions:- For each different database type, different connection properties may be mandatory. So, to support this in rdb-das J2SE connection support, if we know the vendor, we can have programmatic control over which apis to

Re: [DAS]Approach for JIRA-948

Brent and Amita, If we make these updates and connectionInfo becomes XML elements rather then XML Attributes, would this break backward compatibility and make all applications to have to update all DAS XML Config, is this right ? If this is the case, is this acceptable ? -- Luciano Resende

Re: [DAS]Approach for JIRA-948

IMO, at this early stage, we should continue to improve and simplify all user APIs even when this requires breaking changes. How do others feel about this? Thanks. -- Kevin Luciano Resende wrote: Brent and Amita, If we make these updates and connectionInfo becomes XML elements rather then

Re: [DAS]Approach for JIRA-948

I agree.. With only milestone builds out this shouldn't be a big issue. In this particular case, the impact should be limited as it will only affect those who were using the DAS in a J2EE environment. Brent On 12/7/06, Kevin Williams [EMAIL PROTECTED] wrote: IMO, at this early stage, we should

Re: [DAS]Approach for JIRA-948

Amita, Thanks for working on this. One thing I would like to see is the DataSource properties seperated from the J2SE Connection properties. Maybe something like: ConnectionInfo managedtx=true DataSource jndiName=jdbc/myDataSource/ /ConnectionInfo or ConnectionInfo ConnectionProperties

Re: [DAS]Approach for JIRA-948

Luciano, I'm referring to the changes to the DAS config model in Amita's patch. Brent On 12/6/06, Luciano Resende [EMAIL PROTECTED] wrote: Hi Brent, are you recommending these changes in the SCDL ? Or in the DAS config itself to better handle other types of connections in J2SE environments ?