type |
comment |
response |
status |
Samples |
- The samples can be made more useful by having documentation describing what the samples do and how they were built
- add some comments in the artifacts in those samples bundled with Tuscany, that will be very helpful for new comers including me.
- up to date examples and tutorials. Some samples/tutorials are out of date.
- Simple use-cases like: "So you want to call a web service outside of the domain, here's what you need to do."
|
|
|
New
Samples |
- Add sample for calling into EJB
- Better examples for async (true pub-sub with ActiveMQ), conversation support, cross-domain, more robust security policy examples (simplest possible example using OpenLDAP, for example)
|
|
|
Docs |
- Extremly improved documentation. uptodat examples and tutorials.
- Better organized documentation, more elaborated documentation
- improve documentation ,package it and we can download.
- Documentation with working examples is the key to adoption
- More documentation, and tips of architecture using SCA
- Clear documentation, and we're yours! I realize looking at code is good - but code+docs is the way to go.
- Examples for how to use SCA. What are the best practices using SCA
|
|
|
usability |
Better error handling messages |
|
|
Feature-OSGI |
- Improved class loading
- Move to OSGi Easy deployment of SCA components
- We want to be able to create Tuscany OSGI bundles but are having a lot of problems with that
|
2.x release |
|
Feature
Persistence |
- DAS is not updated. Hibernate or other JPA integration
- Better integration between OpenJPA and SDO.
|
|
|
Feature
Distribution |
- cross-domain communication
- Support for distributed service discovery Support for QOS
- Distributed domain
- dynamic wiring
|
|
|
Feature
hetrogenity |
- support for Non-Java-Technologies
- We'd also like to interop C++ and C# components and Java components
|
|
|
Feature
Enterprise |
- More enterprise feature support, like transaction
- Support for clustering: load balancing, failover and resiliency
|
|
|
Feature
Rest |
- Bindings and implementation types: C++, C, REST binding, .Net, Flex AMF, tcp and udp, hession, UDDI, spring.ws
- Build a standard distribution for Tomcat, JBoss, Jonas, ..
- Spring call tuscany
- Seamless integration with JBoss
- We need a tuscany management console
- The only thing missing from Tuscany is a binding which uses dynamic discovery, eg. via UDDI.
|
|
|
|
How is your choice of SCA helping your business?
1 At the moment I am looking at the Tuscany solution in order to show with simple examples to the rest of the team how it can be used to develop SOA like style architecture
2 Reduces integration and development costs
3 I thing the SCA is very good, this is couple with SOA Analisys Design Requirements, and its very good, I see the book of Thomas Erl and is easy mapping to SCA. But I need more documentation to best practices using SCA.
4 To support SOA development efforts
5 Same style of developing business logic(in both Java and C++).
6 Low coupling components
7 it's slowing it down
8 For the moment is just R&D. In our mind it should be able to complete(/replace?) a JEE approch
9 better architecture
10 Tuscany and SCA are an excellent platform for research into SOA.
11 It will help us by being able to turn solutions around much more quickly in a more decoupled manner.
12 greater flexibility
13 Low coupling component |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|