THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Section | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||
|
...
|
...
|
- 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.
- Support for Atom using Apache Abdera
Abdera just released their 0.3.0, I've started to look at it and it looks pretty good. I think we should try to port our Atom/RSS binding to it and see how it compares with the Rome library which we are currently using.
|
...
|
- Some clean up of the core runtime invocation and injection mechanism, we can probably simplify and actually remove code in a number of places
- Separate the interface declaration (per service or reference) and interface type (can be shared if used by multiple services or references) and enhance the dynamic interface/operation support
- Improve exception handling accross bindings
- Better support the remote case of binding.sca (marshaling/unmarshaling data, performance optimization, propagation of callable references)
- 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
|
- 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 - things like move to maven gpg and/or release plugin so creating releases doesn't take such an effort
|
- 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)
- 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 and 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 load contribution as a osgi bundle.
- Support classloading schemes for better isolation/sharing/versioning/updating
|
...
- 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
...