Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

SCA Java Roadmap discussion

  • Support for transaction and reliability policies
    Several users have asked for it, and there's now a public draft of the transaction policy spec

...

  • Improve the Eclipse-based tooling support to facilitate developing and testing Tuscany SCA Java applications.
    • What other Tooling integration, can we improve? STP?
  • Further improve the Tuscany/Geronimo integration to better leverage the SCA domain/node

...

  • Distribution improvements - conclude the ML discussion from a while back on the size and ease of use.
    • Think about profiles for Tuscany SCA use.
  • Further improve SCA policy support. Good support for things like WS-Security and WS-RM and show using Java/JMS/WS etc and all the QOS stuff really is as easy as just saying something like requires="reliability"

...

  • Support classloading schemes for better isolation/sharing/versioning/updating
  • Look into what level of integration with php SCA implementation can be achieved
  • Domain
    • Integrate domain support into all hosting options
    • Support for updates.
    • Look at implication of policies on behaviour of domain
    • Improve node selection algorithm which currently just finds a free node. Would like a node to advertise capabilities (a list of supported extensions/policies?)
    • contribution deployment. currently a node expects a contribution to be available locally. Could do with hook into 3rd party mechanisms that put contribution there
    • Load balancing
    • Failover
    • Resilience, e.g. have domain handle events reported by nodes, e.g. error conditions or complete node failure.
  • Management
    • Link domain/node into established management solution. New modules required management, management-wsdm, management-jmx, etc.
  • implemenation.xslt
  • ESB connectivity, e.g. Mule, Synapse, Servicemix
  • Fix sample ant file production - there is a JIRA for this already
  • Consumability/Usability push - there are JIRAs open specifically about this
  • Some flexibility in the way that endpoints are set on callable references