Please see the prototype in https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/amita/sca, the README under implementation-data-sdo will have details.
Regards, Amita On Jan 8, 2008 5:03 PM, Amita Vadhavkar <[EMAIL PROTECTED]> wrote: > Making a separate mail thread as it is no more talking about web service. > Old mail ref - > http://www.mail-archive.com/[email protected]/msg26764.html > > Some more comments and need suggestions about implementation-data-sdo. > > To keep the interface Collection simple as it is now, internally K(key) > can be checked for delimiter separated list of Strings e.g. comma, > to take care of compound PK, a common situation when it comes to DBs. This > can be checked in impl-data-sdo. > > In .composite implementation.sdo can have attribute "key" as well, e.g. > <tuscany:implementation.sdo table="COMPANY" key="PRODUCTID,ORDERID"> This > can be the way to get to know the PK columns. Convention like DAS can be > used like - > in absence of "key" attribute , it can be assumed to be single column > "ID". > > For the above necessary places like SDOImplementation will have > get/setKey() > > Assume that SDO Type and Property names are same as Database Table and > Column names for simplicity. i.e. do not go into mapping these two. > > In query(string), assume that the params values are hardcoded in WHERE > clause, i.e. no need to pass params later. > > put(K, D) //i.e. update - D should be taken from a DataGraph having > ChangeSummary e.g. > Object result = dataService.get(id); > ((DataObject)result).getDataObject("COMPANY[ID=50]").set("NAME", "MY > ABC"); > dataService.put(List{50}, result); > > Regards, > Amita >
