>
>
> One alternative is to find a way to share some of the jars between
> runtimes,
> eg, if the standalone distribution includes all the jars then it is
> possible
> to get Tomcat deep integration to work running off those jars outside of
> the
> Tomcat install. So that way we could have both the standalone and tomcat
> deep integration working from one 30 meg download sharing dependency jars
> and a single sca contribution repository with all the samples, and only a
> little manual configuration required in Tomcat.
>
We also need to ensure that it easy for people to add extensions that are
not shipped with Tuscany to the classpath. So we have a number of different
building blocks that are combined to form a given runtime
Runtime | Domain/Node | Tuscany Core | Shipped Extensions | Other
Extensions
Can we ship
1. A binary that provides what we have been calling "standalone" along with
all of the jars as it does at the moment.
2. A tool that will
deploy deep integration
build a web application including tuscany
Not sure about tuscany as a war.
Simon
