type

comment

response

status

Samples

  1. The samples can be made more useful by having documentation describing what the samples do and how they were built
  2. add some comments in the artifacts in those samples bundled with Tuscany, that will be very helpful for new comers including me.
  3. up to date examples and tutorials. Some samples/tutorials are out of date.
  4. 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

  1. Add sample for  calling into EJB
  2. 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

  1. Extremly improved documentation. uptodat examples and tutorials.
  2. Better organized documentation, more elaborated documentation
  3. improve documentation (smile)，package it and we can download.
  4. Documentation with working examples is the key to adoption
  5. More documentation, and tips of architecture using SCA
  6. Clear documentation, and we're yours! I realize looking at code is good - but code+docs is the way to go.
  7. Examples for how to use SCA. What are the best practices using SCA

 

 

usability

Better error handling messages

 

 

Feature-OSGI

  1. Improved class loading
  2. Move to OSGi Easy deployment of SCA components
  3. We want to be able to create Tuscany OSGI bundles but are having a lot of problems with that

2.x release

 

Feature
Persistence

  1. DAS is not updated. Hibernate or other JPA integration
  2. Better integration between OpenJPA and SDO.

 

 

Feature
Distribution

  1. cross-domain communication
  2. Support for distributed service discovery Support for QOS
  3. Distributed domain
  4. dynamic wiring

 

 

Feature
hetrogenity

  1. support for Non-Java-Technologies
  2. We'd also like to interop C++ and C# components and Java components

 

 

Feature
Enterprise

  1. More enterprise feature support, like transaction
  2. Support for clustering: load balancing, failover and resiliency

 

 

Feature
Rest

  1. Bindings and implementation types: C++, C, REST binding,  .Net, Flex AMF, tcp and udp, hession, UDDI, spring.ws
  2. Build a standard distribution for Tomcat, JBoss, Jonas, ..
  3. Spring call tuscany
  4. Seamless integration with JBoss
  5. We need a tuscany management console
  6. 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

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 
  • No labels