Ant, some comments are below: Please note, the comments below are based on experiences with Tuscany v 0.9 - 1.0.1.
*- Do you use and are happy with the current distributions? * As of 1.0.1, there were a large amount of JARs included with the distribution but depending on how Tuscany is used could not be required (i.e. Jetty). Increased documentation on how to reduce the JAR footprint would be beneficial. In some cases, JARs needed to be removed to get Tuscany functional on some application servers. *- Do you use the binary distribution or build your own out of individual jars? * Some small changes to Tuscany code was required which necessitated the need to compile from source. Due to some incorrect (dead) links in the Maven build script, this effort proved troublesome. A workaround is to use a local Maven repository however additional maven configuration is required. *- Do you run Tuscany standalone, or use it it webapps, or embed it in other runtimes? * Webapps, Was used with Tomcat and Websphere, not standalone. *- Do you find it easy or hard to upgrade to new Tuscany releases? * Yes, due to some API changes (Tuscany Servlet vs Filter) some modification of the Tuscany runtime was required (for our use). (Version 0.99 -> 1.0) *- Is it a problem working out what Tuscany jars and dependency jars are needed?* Yes, see above. -- Chuck Balders
