| Section |
|---|
|
| Column |
|---|
| | Panel |
|---|
| borderColor | #C3CDA1 |
|---|
| bgColor | #ECF4D1 |
|---|
| titleBGColor | #C3CDA1 |
|---|
| title | Java SCA Roadmap |
|---|
| borderStyle | solid |
|---|
| |
| Anchor |
|---|
| About This Page |
|---|
| About This Page |
|---|
|
| Background Color |
|---|
| | About This Page |
This page contains a list of features that our community thinks is important to include in Tuscany Java |
|
...
SCA. Items can be linked to a more detailed Roadmap page as they are being worked on. Please help to make this a live document. Thanks
Interested to help? Great! We look forward to your participation. Start by posting your thoughts on the developer mailing list. You can subscribe to the developer mailing list here | Anchor |
|---|
| Programming Model |
|---|
| Programming Model |
|---|
|
| Background Color |
|---|
| | Programming Model |
- Update the policy model to separate it from the assembly model http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Policy
- Extend the runtime wires to allow the binding to contribute wireFormat and operationSelection interceptors http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Request+Response+Binding
- Endpoint implementation needs fixing up to take account of this
- Roll endpoint implementation out to services
- Can it replace $promoted$?
- Support rpc/literal wsdl
- Support for transaction and reliability policies
- Several users have asked for it, and there's now a public draft of the transaction policy spec
- 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"
| Anchor |
|---|
| Implementation Types |
|---|
| Implementation Types |
|---|
|
| Background Color |
|---|
| | Implementation Types |
- Get implementation.bpel more spec complete
- Webapp and EJB module integration
|
|
...
- Better integration btw script components and bindings and data bindings to show the dynamic language support really does have value - seamlessly wire up Ruby components using Hpricot for HTML processing with binding.http, JavaScript/E4X for XML manipulation with binding.ws etc
- Interoperability: Improve using sca wdsl with X language
(replace X with
java, Python, C++, ecc)
| Anchor |
|---|
| Integration with other technologies |
|---|
| Integration with other technologies |
|---|
|
| Background Color |
|---|
| | Integration with other technologies |
- 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.
- ESB connectivity, e.g. Mule, Synapse, Servicemix
- Finish off web2.0 support
- Incremental binding.ws improvements
- 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
- 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
|
|
...
...
...
...
| Background Color |
|---|
| | Usability |
|
|
- 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
- Rationalize the pass-by-value interceptors
- 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
- 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
...
- Documentation that matches releases. Right now there is only one documentation, the latest.
- 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)
- 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.
- Management
- Link domain/node into established management solution. New modules required management, management-wsdm, management-jmx, etc.
- Add some sort of mediation capability
- Data Integration, as I see SCA of great help to simplify exposing data as services to a client application in a simple and flexible way
|
|
...
- Improve the error reporting/handling for our data binding framework.
...
- 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
|
|
...
...
- 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.
- 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
...
