Hi
2.x is becoming active again so what are people hoping to get done for
M3? I'm interested in continuing to enhance the level of OASIS support
we have so to that end I took a look at the OSOA vs OASIS page [1] to
try and identify the big items that need fixing. The following jump
out...
Assembly - based on spec JIRA [2]
ASSEMBLY-1 / ASSEMBLY-17 / ASSEMBLY-57
All about sorting out reference resolution (implies finishing up
our endpoint support)
ASSEMBLY-8 Artifact resolution
Pushes us to finish tidying our contribution workspace re-factoring
ASSEMBLY-79 wireFormat/operationSelector
Need to bring in binding wire support from 1.x
Could bring in binding.jms or
OASIS also have the spec compliance tests done now so we can
exploit those to see how many we could get running. I know Kelvin has
been trying them out but I don't know how many need to be fixed.
Other things that have been bouncing around the list recently and
which would be good to get on with....
Binding.ws
A reorg here has just been mentioned on another thread and would
motivate us to bring in the binding wire and also get policy working.
Java - spec only just going out now so no tests yet
SCA client
API changes and simplification
Policy
Model is in place
Runtime code needs doing
Other
Error handling
I notice from some of his recent posts that Mike is getting
frustrated by the lack of context we provide in out error messages,
i.e. which composite/component/binding etc. is being processed.
Now would be a good time to improve that
We could also take the opportunity to refresh the validation
tests and locate then with the module being tested rather than being
in one large itest.
Backward compatibility
I've just started to look at this again to see what we could do.
Anything here that sparks your interest? Alternatively what other
things would be good to get into M3?
Simon
[1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/OSOA+SCA+vs+OASIS+SCA
[2] http://www.osoa.org/jira/browse/ASSEMBLY
