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

...

• Conversational and non blocking + callback programming model over Web2.0 bindings
  Seems like a good fit with JSON for example... in particular Ajax interactions fit really well with the SCA non blocking + callback programming model.Ability to model client side JavaScript components
  Looking at the Store sample for example, I'd like to be able to model the client Javascript as a component with SCA references to the ShoppingCart and Catalog services, instead of manually creating JSON and Atom client proxies in the client Javascript code.
• Bring binding.jms to spec 1.0 level (and what about JCA as the 1.0 spec is out?)

• Add support for JSONRPC reference binding so that SCA components can talk to JSONRPC services

• Better align the WSDL2Java tools with Axis2

• Leverage the Axis2 JAX-WS metadata layer for better WSDL/Java interop and the WSDL-less support

• 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

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

• Fix all the build issues (maven 2.0.6/2.0.7/JDK6/empty repository) so new users building Tuscany have a good experience

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

...

• clean up the WS and tooling code so we don't copy so much Axis2 code as it causes such a headache when moving up Axis2 releases and picking up Axis2 fixes

• Get binding.jms more spec complete. Get implementation.bpel more spec complete

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

...

• Improve the error reporting/handling for our data binding framework.

• Support hot deployable on contribution and composite.
  This should be have a recursive algorithm to update the correlated component when it has been referenced.Support SDO namespace when using websservice.
  Deploy a service to webservice,a schema file used in SDO and have sdo namespace such as commonj.sdo/java or commonj.sdo/xml,we should support the feature when parsing the wsdl.

• Support load contribution as a osgi bundle.Support classloading schemes for better isolation/sharing/versioning/updating

• Look into what level of integration with php SCA implementation can be achievedDomain
• 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.

...

• 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

• Fix the callback and conversations protocol for Web services so that it complies with WS-Addressing (TUSCANY-1849)

• Clean up the RuntimeWireInvoker code so that it does not duplicate code in JDKInvocationHandler

• Eliminate unnecessary cloning of wires and bindings on the invocation and callback paths

• Fix remaining minor loose ends in callback support

• Remove restrictions from exception support over the Web services binding