TODOs for Java SDO
DevelopmentItems
- 2.1 Spec implementation
- Community Test Suite
- Documentation
Here are some items that are important, please feel free to add your own items or start a discussion on the tuscany-dev mailing list.
Work Item Description |
Interested in tackling |
Jira (if any) |
Documentation |
Notes |
Change Summary Serialization |
Frank Budinsky and Yang Zhong |
|
|
|
Community Test Suite |
Dan Murphy Taking the lead, lots of scope for input |
|
|
|
dynamic subclasses of generated type |
I've got this on my radar unless someone else gets there first (Kelvin) |
|
|
|
utility to retrieve URI from a factory |
|
|
|
|
Add a new codegen option to generate static SDO APIs using StAX parser |
|
|
1 |
|
support ability to unregister types in a namespace |
|
|
|
|
update UML diagrams on website |
|
|
|
|
rearrange source to reflect extensions and dependencies |
|
|
2 |
|
load and save XML using JAXP Source and Result |
|
|
2.1 specification |
|
Nullable property control |
|
|
2.1 specification |
|
sdoXML:many XSD annotation |
|
|
2.1 specification |
|
open content property creation |
|
|
2.1 specification |
3 |
ClassLoader issues with SDO |
|
|
|
|
SDO URI serialization |
|
|
|
|
Big Bank failing in SDO serialization |
|
|
ought to get the samples back up to running status asap, but at the time or writing there is a failure upstream of this failure according to ant |
|
desc |
who |
doc link |
|
Notes
- 1 Chunky interesting piece of work, requires knowledge of StAX + Java emitter syntax (similar to JSP)
2 This could be more than just sorting out the java level dependencies, it gives rise to the question of whether we should divide up the source so that there is an option extras section which would contain things like this, that bering in extra dependencies, e.g. the recently proposed move of Java2WSDL and WSDL2Java from SCA into SDO 3 Some of this is done, but some tests would be good, and there is on-demand open content property creation to implement
Things to Check
When asking a data object or a change summary for its DataGraph, how do we handle the case where the DataGraph is an instance of DataObject with type namespace = "commonj.sdo" and type name "DataGraph". Following on from that, what semantically is the root data object when such a DataObject is at the root of the data graph?
Release Process
New Features Since M2
TUSCANY-XXX |
explanation |
JIRAs fixed since M2
TUSCANY-XXX |
explanation |