On 5/17/07, Simon Laws <[EMAIL PROTECTED]> wrote:
Currently the sample overview section of the samples/README contains some very high level words about what samples we have but nothing to guide the user in. Ant suggested on the IRC that we add and ordered list. How about the following order calculator - A calculator build with java components and local wires simple-bigbank - A banking application built with java components and local wires calculator-script - The calculator but this time built using various script languages calculator-web - The calculator again but this time running inside a web app helloworld-ws-reference - The client side of a hello world sample that uses a web service binding helloworld-ws-service - The server side of a hello world sample that uses a web service binding calculator-rmi-reference - The calculator configured to talk RMI to the calculator-rmi-service samples calculator-rmi-service - The calculator configured to accept RMI requests from calculator-rmi-reference helloworld-jsonrpc - An SCA application that exposes service using JSONRPC implementation-composite - An SCA application that shows how composites are used to implement components simple-callback - An SCA application with two components demonstrating the callback interface supplychain - A more complicated sample showing how asynchronous callbacks can be used databinding-echo - An SCA application that shows how databindings transform data implementation-crud - Shows how to build new implementation type extensions implementation-crud-client - A sample application that exercises the new implementation extensions binding-echo - Shows how to build new binding extensions binding-echo-appl - A sample application that exercises the new binding extension Simon
This seems like a good thing to do to me. Also how about breaking the list up by inserting after supplychain a comment saying the remaining ones are samples showing how to extend the Tuscany runtime? ...ant
