...

• Finish of Sprng spec support - TODOs

2.x

2.0 - M1 - OSGi Runtime

• Define and package a clean SPI
  • Identify the SPIs
  • SPI improvements that have appeared on the wiki and various threads
    • Endpoint TUSCANY-2809
    • Builders
    • Binding wire providers
    • ?

• Tuscany delivery story (end to end)
  • developing core
  • developing extension
  • developing samples/demos
  • building and releasing a distribution, how do we do this much more quickly than we do now TUSCANY-2813launching the tuscany runtime TUSCANY-2810
  • using a distribution, ease of use of samples, tooling integration etc.
  Domain/Node TUSCANY-2811
  • Use scenarios to better understand how domain/nodes are used
    • multiple contributions installed to a SCA domainc
    • cross-contribution artifact reference resolution
    • node configuration to represent runtime capabilities
    • nodes running SCA composite applications.
  • Decompose the basic services related to SCA domain management and provide SPIs for these atomic operations.

• How to adopt OASIS spec features (2 functional)
  • what features have changed
  • how to do changed features map to compliance testing
  • how to extend the infrastructure, XSD, processors, runtime, tests
  • how to do compliance testing
  • how to improve our documentation

• Extensions
  • implementation.java
  • binding.sca
  • binding.ws
  • TBD

• Scenarios
  • samples/calculator
  • samples/calculator-webapp
  • samples/calculator-equinox
  • TBD

2.0 - M2 - Assembly compliance

• XSD/API

• Processors

• Assembly compliance tests

• Policy

• Endpoint TUSCANY-2809

• launching the tuscany runtime TUSCANY-2810

• Turn callback support into interceptors TUSCANY-2808

• Domain/Node TUSCANY-2811
  • Use scenarios to better understand how domain/nodes are used
    • multiple contributions installed to a SCA domainc
    • cross-contribution artifact reference resolution
    • node configuration to represent runtime capabilities
    • nodes running SCA composite applications.
  • Decompose the basic services related to SCA domain management and provide SPIs for these atomic operations.

• Any other infrastructure fixes we come across required for OASIS compliance

2.0 - M3 - Policy/Extension compliance

• Ws compliance tests

• Java compliance tests

• More policy work + Policy compliance tests

• More Domain/node work + Assembly compliance tests relating to domain

• Bring in remaining OASIS specific extension on upgraded infrastructure, e.g.
  • JMS, JEE, BPEL, EJB binding, Spring (is there anything else) + compliance tests

2.0 - M4 - Tuscany extensions

• On top of OASIS compliance bring in any Tuscany specific extensions we think we need?

2.0 - Beta

• Lock down and prep for branch