Hi, I am trying to understand DAS for last couple of weeks and thought that below may be helpful to make DAS more generic.
1) Oracle database support? - Are we not going to consider this 2) Support for working with J2SE - connection support - this way standalone applications can also benefit from DAS 3) Is it better to follow conventions in forming command name, it can be helpful in Declarative DAS development. 4) Some abstraction layer provided by DAS to shield the usage of SDO. So behind the curtain, DAS can be flexible between using SDO or another data representation. 5) Same thing applies to RDB, non-RDB. So, the SCA-DAS integration effort can be based on these abstractions instead of dealing with SDO, RDB directly. Regards, Amita On 11/22/06, Brent Daniel <[EMAIL PROTECTED]> wrote:
Hey Luciano, A few updates.. I committed some changes to the MySQL test suite yesterday to solve the problems with the dog kennel tests and one of the stored procedure tests (Sorry, I didn't realize there was a JIRA for it.) Things should run fine now. The default OCC policy has been in for a while now (I don't think it made M2 but is in the trunk.) I hope to put in OCC recovery support this week while I have some time to work on it. Thanks, Brent On 11/21/06, Luciano Resende <[EMAIL PROTECTED]> wrote: > With the M2 release out, I'd like to look forward to things that we want to > do next for DAS. > > I think that there are still couple things that we can improve our core DAS > features, like improving our Optimistic Concurrency Control support, improve > the performance of our pager api and review our MySQL support as I have > noticed some test failures recently. > > As for our history with SCA integration, we have started efforts around > Declarative DAS, and this is probably another area we would like to continue > to work going forward. This effort would probably also contribute to our > samples, as I'd assume we would create some simple samples consuming these > new ways of using DAS. > > I also think we should continue to improve our user documentation and > distribution infrastructure to make our release cut easier. > > Below is a summary list of items and JIRAs that are related to these > possible items : > > DAS Core features'' > - Optimisc concurrency control > - Support for OCC recovery (TUSCANY-916) > - Default OCC policy (all OCC-capable fileds used in overquaified > "where") > - More performant pager (TUSCANY-542) > - Review MySQL Support (TUSCANY-937) > > - SCA Intgration > - Expose DAS as a Pojo SCA Service (impl.java) (TUSCANY-898) > - Container-based DAS (impl.das) (TUSCANY-904) > > DAS Samples > - Sample consuming DAS as a Pojo SCA service > - Sample consuming container-based DAS > > Documentation > - Continue to work on DAS User's guide > - HOW-TO describing how to build a DAS Application > > Infrastructure > - Automate release distribution process > > > This is just of brain dump of where my thinking is at the moment, I'm sure > everyone has their own thoughts about things we should tackle. > It would be good to get to them all on the table :-) > > > -- > Luciano Resende > http://people.apache.org/~lresende > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
