> > I think we need to keep in mind the bigger overall picture when thinking > about these details, if we've been getting too much into the > implementation > detail would help to step back a bit - the following are the things i > think > we're trying to do here: > > 1) applications to contain only the code and other artifacts required for > the application itself not Tuscany internals - simple sca contribution > jars > > 2) some sort of runtime(s) which can run those application contribution > jars, so that could be things like standalone (command prompt), from > testcases, in a webapp, or some customization of something like > Tomcat/Geronimo/WebSphere/JBoss etc > > I think we also need: > > 3) Those runtimes need to be distributed but the Tuscany download page > should have a small number of downloads so its easy for users to work out > which to choose > > 4) To make it easy for newbies to run things so at least one distribution > should have prebuilt samples so they can be run out-of-the box without > having to be compiled/built and for things to work without having to do > much/any messing about with installation/configuration/customizing. > > 5) Ideally the easy to use distribution is not so large. > > Do all those sound reasonable? Does anyone want to add/remove/modify > anything? > > ...ant >
Ant I would add the following, which may be and extension of 4) but here goes. Support the automatic running of all sample applications as though they were being run by the user. To allows us to test all forms of the sample applications in all applicable runtimes on a regular basis without leaving it to the point at which we make a release. Simon
