You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <tu...@ws.apache.org> on 2006/08/22 11:51:18 UTC
[jira] Updated: (TUSCANY-650) End-to-end sample application
[ http://issues.apache.org/jira/browse/TUSCANY-650?page=all ]
ant elder updated TUSCANY-650:
------------------------------
Fix Version/s: Java-Mx
> End-to-end sample application
> -----------------------------
>
> Key: TUSCANY-650
> URL: http://issues.apache.org/jira/browse/TUSCANY-650
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SCA Samples
> Affects Versions: Java-M2
> Reporter: Meeraj Kunnumpurath
> Fix For: Java-Mx
>
>
> We need to have a realistic application that demonstrate the end-to-end capabilities of SCA as a technology and Tuscany an implementation platform for building applications using the SOA-paradigm. The big bank example, may serve this purpose. The application should demonstrate,
> 1. Ability to have components realised using different implementation technologies working together in a runtime as part of a coherent application. For example, a component written in Java talking to a component writtern in groovy taling to a component realised as a database stored procedure.
> 2. Ability to integrate components through different transport bindings as well as exposing their services to extrenal clients over a variety of transport bindings. For example, a Java component could talk to a Javascript component through the SCA binding and the Javascript component could talk to a database stored procedure through the JDBC binding. The service offered by the Java client itself could be exposed to extrenal mclinets through SOAP/HTTP and JMS bindings.
> 3. Ability to enforce QoS aspects and policies like security, transactions, reliability etc.
> I think the first thing to do would be to look at the big bank sample in detail and see whether it fits the bill. If it does, we can elaborate the scenarios and identify the components, the preferred container types for the components, invocation bindings between the components, bindings used to expose the services to external clients. If it does not, we need to come with a realistic application with a coherent set of use cases that can demonstrate the aforementioned capabilities.
> Ta
> Meeraj
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org