Hi Frank, So - it is my understanding that with SDO3 specs and as general direction for SDO - a SDO implementation is expected to provide the whole stack, SDO API + persistence services. I remain with a question on SDO 2.1 JAVA implementation by Tuscany. How can this code be reused if one wants to plug-in a bridge to a persistent storage ? In other words - is there TUSCANY documentation or pointers to those "low level features" you mention? Can anyone please enlist a set of Tuscany SDO JAVA classes where one should look for pluging-in a bridge to persistence? Thanks, Shmuel Coller From:Frank Budinsky [mailto:[email protected]] Sent: Monday, August 24, 2009 6:15 PM To: [email protected] Subject: Re: boundary between DAS and SDO implementation Hi Shmuel,
SDO does not provide any interfaces to plug in a DAS. Instead, it just provides the low level features that allow, among others, disconnected-data applications (e.g., DAS like apps) to be built on top of it. In fact, the latest version of SDO being worked on at OASIS (SDO 3) doesn't mention DAS anymore, it simply refers more generally to "persistence services", of which DAS could be one. Standardization of a formal DAS spec doesn't seem to have gained very much traction, although I believe DAS is still being informally discussed by a few companies at OSOA (not OASIS). Frank. Shmuel Coller <[email protected]> wrote on 08/23/2009 08:12:49 AM: > Hello from a newcomer, > It is not clear to me if Tuscany implementation for SDO has a well > defined boundary where one can plug a self written DAS. > I am interested to learn this issue - also at the level of SDO > specs by Oasis TC . > For example - are there Java interfaces that a DAS should implement > so that a DAS can serve alongside (and reuse) an available SDO > implementation ? > Shmuel Coller
