SCA Java Roadmap discussion

Key

done
being worked on
to be in 1.1

Items

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

...

• Website documentation. There's still lots of detail and improvements we could add to the documentation and its really important to attract users

• Resolve JIRAs. Be good if we could all commit to trying to resolve at least a couple of these each week if we're to make much of a dent in the 150
  open ones.

• Fix nightly builds (looks like this may be going again now)

...

• Make releasing easier
  • move to maven gpg and/or release plugin so creating releases doesn't take such an effort
  • automate sample ant script production

• 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"

• Incremental binding.ws improvements (MTOM, headers, REST/POX etc)

...

• For JMS maybe have a host-jms module so you don't have to start a separate JMS server or can use the the Geronimo one if thats where Tuscany is running

• Get the Geronimo integration and WAR distribution working really well and with all Tuscany extensions so you can take a Tuscany sample contribution jar and it easily runs where ever you deploy it.

...

• 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

...

• Consumability/Usability push - there are JIRAs open specifically about this

• Some flexibility in the way that endpoints are set on callable references

...