Work for this release is being tracked under TUSCANY-1171
Using my M2 post mortem notes to drive the process and updating them here
Here are the issues fixed in Milestone 3 (so far)
Test | TUSCANY-1100 | Dynamic Type tests are needed to ensure that all XSD datatypes are supported | Java SDO Implementation | Major |
New Feature | TUSCANY-1101 | Support mixed Sequence and any Sequence in Change Summary | Java SDO Implementation | Major |
New Feature | TUSCANY-1082 | Change Summary XML deserialization | Java SDO Implementation | Major |
New Feature | TUSCANY-930 | Add new SDOUtil.createHelperContext() method | Java SDO Implementation | Major |
New Feature | TUSCANY-929 | Move to SDO 2.1 spec APIs | Java SDO Implementation | Major |
New Feature | TUSCANY-713 | Discover and regiester new SDO types during the time of loading the XML instance document | Java SDO Implementation | Major |
New Feature | TUSCANY-684 | Generated SDO classes should be able to register the static types to a given TypeHelper | Java SDO Implementation | Major |
Improvement | TUSCANY-1113 | Extensible namespaces and types that change | Java SDO Implementation | Major |
Improvement | TUSCANY-1107 | Multiple calls to getNamespaceContext | Java SDO Implementation | Major |
Improvement | TUSCANY-1091 | DataObjectXMLStreamReader doesn't have to repeat NameSpace declaration which impacts performance | Java SDO Implementation | Major |
Improvement | TUSCANY-1088 | SDO should tolerate malformed XML | Java SDO Implementation | Major |
Improvement | TUSCANY-1086 | Scope defined java serialiazation/deserialization of SDO | Java SDO Implementation | Major |
Improvement | TUSCANY-1083 | Shorter NameSpace prefix to speed up XML processing and reduce communication bandwidth | Java SDO Implementation | Major |
Improvement | TUSCANY-928 | Define Tuscany SDO options for XMLHelper load and save operations | Java SDO Implementation | Major |
Improvement | TUSCANY-521 | Hide special Sequence-type properties from SDO Types | Java SDO Implementation | Major |
Improvement | TUSCANY-709 | Loads DataGraph in designated scope(TypeHelper) | Java SDO Implementation | Minor |
Bug | TUSCANY-1093 | "isSet returning false when boolean set to false, or int set to 0" | Java SDO Implementation | Critical |
Bug | TUSCANY-1132 | SDO Java serialization/deserialization throws an exception when the serialized data object is not the root and its container is of AnyTypeDataObject | Java SDO Implementation | Major |
Bug | TUSCANY-1130 | Concurrent access to SDOUtil.createHelperContext() results in exception | Java SDO Implementation | Major |
Bug | TUSCANY-1099 | fix for TUSCANY-1083 used lookupPrefix method of Node not available to Java 1.4.2 users | Java SDO Implementation | Major |
Bug | TUSCANY-1097 | DataObjectXMLStreamReader shouldn't have ignored (transient Properties in) Sequence | Java SDO Implementation | Major |
Bug | TUSCANY-1085 | schemaLocation attribute in the <xsd:import> should be only a hint | Java SDO Implementation | Major |
Bug | TUSCANY-1062 | DataGraph.createRootObject implementation does not match 2.1 spec and also is not helpful when given bad parameters | Java SDO Implementation | Major |
Bug | TUSCANY-1044 | DataHelperImpl.toDateTime() is not compliant with spec. | Java SDO Implementation | Major |
Bug | TUSCANY-972 | commonj.sdo/xml namespace should be supported by SDO runtime by default | Java SDO Implementation | Major |
Bug | TUSCANY-958 | NPE generated during a property set of a static SDO | Java SDO Implementation | Major |
Bug | TUSCANY-956 | SDOFactory instance lookup is using the wrong namespace URI | Java SDO Implementation | Major |
Bug | TUSCANY-935 | "SDO path accessors need to support names that contain "".""" | Java SDO Implementation | Major |
Bug | TUSCANY-932 | Invoking DataObject.isSet(String path) with invalid path would result in NPE | Java SDO Implementation | Major |
Bug | TUSCANY-931 | "Sequence.add(int index, String propertyName, Object value) is not functioning correctly" | Java SDO Implementation | Major |
Bug | TUSCANY-894 | SDO (and indirectly DAS) may not now depend on CPL if EMF has completed migration to EPL | Java SDO Implementation | Major |
Bug | TUSCANY-887 | TypeHelper.define() should create an accompanying global property per type | Java SDO Implementation | Major |
Bug | TUSCANY-859 | ChangeSummary#isCreated cache is not updated while changes are still going on | Java SDO Implementation | Major |
Bug | TUSCANY-836 | doubleValue() may be inaccurate for Long | Java SDO Implementation | Major |
Bug | TUSCANY-396 | Cardinality of wildcard element not respected | Java SDO Implementation | Major |
Bug | TUSCANY-1055 | DataFactory.create(abstract_type) should throw an IllegalArgumentException | Java SDO Implementation | Minor |
Bug | TUSCANY-885 | Property DataObject.getProperty(String propertyName) should return null if the property cannot be found | Java SDO Implementation | Minor |
Bug | TUSCANY-701 | Conversion to date types which do not include month can give incorrect results | Java SDO Implementation | Minor |
New Feature | TUSCANY-1102 | Support EMF 2.2.2 | Java SDO Implementation, Java SDO Tools | Major |
Bug | TUSCANY-1123 | test case generated code and metadata access is anachronistic | "Java SDO Implementation, Java SDO Tools" | Major |
Improvement | TUSCANY-1155 | Java SDO static code generation tool java doc and usage hints need updating. | Java SDO Tools | Minor |
Bug | TUSCANY-1141 | The dependency/imported package was not initialized if the codegen tool was provided with -javaPackage option for the target codegen package | Java SDO Tools | Major |
Bug | TUSCANY-1120 | Static code generator template bugs | Java SDO Tools | Major |
Bug | TUSCANY-1050 | "For some schemas, the code generated will not compile (notication and settable problems)" | Java SDO Tools | Major |
Bug | TUSCANY-934 | XSD2JavaGenerator -noEMF option does not work with abstract classes. | Java SDO Tools | Major |
Bug | TUSCANY-933 | XSD2Java Generator still generates EMF codes with -noEMF option on | Java SDO Tools | Major |
Bug | TUSCANY-718 | make -noEMF code generation the default | Java SDO Tools | Minor |
Here are the release process steps harvested from the M2 release
May 9th, 2007, SDO Java achieves state of being a functionally complete implementation of the SDO 2.1 specification
This was achieved at code revision level 536331. The community is working towards a new SDO release after a period
of enhancing the test suite and making bug fixes.
May 2nd, 2007, SDO Java beta1 release requests ratification from the IPMC as a final stage before announcement.