In Part 1 of this article we introduced SDO, looking at its origins and then
reviewing some of its features through a scenario based on medical
investigations. In Part 2 we'll go on to examine further features of SDO in
such a way as to add property values to a data object beyond those explicitly
defined by its type, the ability to record changes made to the data graph, a
more elegant way to create types programmatically, and the ability to extend
datatypes at runtime.
Our examples will depend on two XML Schema definition files that we'll
reproduce here. The full details of the scenario they represent were
presented in Part 1. These listings are available at
http://gemsres.com/story/dec06/313547/source.html.
Part 1 of this article was published when version 2.01 of the SDO
specification was current. Since then v2.1 has been released, however, in
this article we'll... (more)
Service Data Objects (SDOs) simplify and unify Service Oriented Architecture
(SOA) data access and code.
SDO complements the strength that SCA (Service Component Architecture) offers
for simplifying development of SOA-based solutions. SCA handles the
composition of service networks and SDO focuses on simplifying data handling.
These technologies are getting significant support in the industry. The
development of the SDO and SCA specifications is in the hands of the Open
Service Oriented Architecture collaboration (www.osoa.org) and open source
implementations of these specificat... (more)