SDO 1 had lots of "implementation dependent" APIs, that have been replaced by standard APIs in SDO 2, so moving from SDO 1 to 2 requires some porting effort.
You should ask questions about the SDO 1 implementation in IBM RAD 6 on the EMF newsgroup at Eclipse: news://news.eclipse.org/eclipse.tools.emf Frank. "António Mota" <[EMAIL PROTECTED]> wrote on 03/28/2007 08:28:20 AM: > Hi. > > Thanks for your answer. So, from what i understand, the version of SDO > i'm using with IBM RAD 6 is that version 1 that is now deprecated? Is > it possible to substitute that IBM version with the current Tuscany > version? > > Other thing, is it OK if i ask questions directly related to the IBM > RAD SDO version in this mailing list? Do you know another place, since > IBM thinks that that is not necessary? ( > http://www-128.ibm.com/developerworks/forums/dw_thread.jsp? > message=13790505&cat=24&thread=105205&treeDisplayType=threadmode1&forum=339#13790505 > ) > > Thanks for your help. > > > > > 2007/3/27, Frank Budinsky <[EMAIL PROTECTED]>: > > SDO is a specification developed by an industry consortium (OSOA). The > > current version of the specification is 2.1 and can be found at > > http://osoa.org. > > > > Several companies have implementations of SDO in their products including: > > BEA, IBM, Oracle, SAP, RogueWave, XCalia. IBM's implementation of SDO > > version 1 was done at Eclipse, but that project has since been deprecated > > and moved to Apache (Tuscany). Tuscany is currently implementing SDO 2.1. > > There is also an Oracle implementation of SDO that was recently proposed > > for Eclipse (the EclipseLink project). It will also be SDO 2.1, but with > > different features and performance characteristics than Tuscany. > > > > In terms of standardization, SDO for Java is going to be standardized via > > the JCP (JSR 235). Other languages are moving to OASIS. > > > > Frank. > > > > "António Mota" <[EMAIL PROTECTED]> wrote on 03/27/2007 10:24:51 AM: > > > > > Can someone please enlight me about these SDO things? > > > > > > I've worked in a project a year ago where i used IBM RAD with JSF and > > > SDO Relational Records and Relational Record Lists. At that time i > > > searched the web for material and found almost nothing valuable, but i > > > did got the impression that SDO was a "proprietary" technology that > > > IBM and Oracle and a few other minor players decided to implement > > > without the approval of the JCP/Sun and so it was not part of J2EE. > > > > > > I did found the technology to be very interesting, but due to the lack > > > of support and information (among other factors) the work did not went > > > well and was interrupted in the middle. > > > > > > Now, one year after, i suggested again the use of IBM RAD with JSF and > > > SDO in a shop that works almost exclusively with IBM technologies. > > > Despite my bad experience with it. But i found that the information > > > and support still doesn't practically exist. > > > > > > However, now i found references to SDO not only with IBM and Oracle, > > > but also in relation to some other vendors, PHP, and more confusing > > > with Eclipse and Apache... Oh, and OSOA too.. > > > > > > So my question is, is all these SDO the same thing? Are IBM and Oracle > > > and Eclipse and Apache developing the same thing in different ways? > > > Did they all centralized the development in Apache? If so, IBM RAD > > > have older versions of SDO or their own implementation? > > > > > > > > > I think it's all too confusing... > > > > > > > > > -- > > > Melhores cumprimentos / Best regards > > > António Santos Mota > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Melhores cumprimentos / Best regards > António Santos Mota > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
