[ http://issues.apache.org/jira/browse/TUSCANY-386?page=comments#action_12412077 ]
Kevin Williams commented on TUSCANY-386: ---------------------------------------- Could also simplify the config file: * Update command not needed if DAS allowed to generate CUD * Table definitions not needed if not using aliasing (just take the conventions) * Parameter elements not needed unless specifying type (just take conventions) > BigBank application should demonstrate best-practice use of the DAS > ------------------------------------------------------------------- > > Key: TUSCANY-386 > URL: http://issues.apache.org/jira/browse/TUSCANY-386 > Project: Tuscany > Type: Improvement > Reporter: Kevin Williams > Assignee: Kevin Williams > > The current use of DAS in BigBank could be simplified and changed to better > reflect best-practice use of the DAS. Some initial observations: > 1. Should not use low level commands for inserting new records. Instead, > the change history capaility of the graph should be leveraged and the DAS > should generate the CUD statements. > 2. Use of CommandGroup simplify things. Defining connection properties > there would remove need for application to provide connections. > A few other things should change but depend on existing JIRAs > * Should specify static SDO types on the config used to create the > CommandGroup (this API is not there yet) > * Should not have to artificially provide a graph root. Depends on T-154 > * Should be able to ask DAS to produce a graph from a static > factory-created instance (need a DAS utility for this) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
