THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
...
- Improve the Eclipse-based tooling support to facilitate developing and testing Tuscany SCA Java applications.
- What other Tooling integration, can we improve? STP?
...
- 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
...
- 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.
...
- Fix sample ant file production - there is a JIRA for this already
- Consumability/Usability push - there are JIRAs open specifically about this
...