Differences between revisions 30 and 31
Revision 30 as of 2006-07-24 10:03:13
Size: 5497
Editor: SimonLaws
Comment:
Revision 31 as of 2009-09-20 22:49:02
Size: 5422
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 62: Line 62:
  * [wiki:/ServletClient Accessing a service from a Servlet application]   * [[/ServletClient|Accessing a service from a Servlet application]]
Line 64: Line 64:
  * [wiki:/JSPClient Accessing a service from a JSP application]   * [[/JSPClient|Accessing a service from a JSP application]]
Line 66: Line 66:
  * [wiki:/JSFClient Accessing a service from a JSF application]   * [[/JSFClient|Accessing a service from a JSF application]]
Line 68: Line 68:
  * [wiki:/SpringClient Accessing a service from a Spring web application]   * [[/SpringClient|Accessing a service from a Spring web application]]
Line 72: Line 72:
  * [wiki:/EagerInit Creating a simple component]   * [[/EagerInit|Creating a simple component]]
Line 74: Line 74:
  * [wiki:/SpringComposite Scenarios for creating and wiring Spring composites]   * [[/SpringComposite|Scenarios for creating and wiring Spring composites]]
Line 78: Line 78:
  * [wiki:/TwoComponents Demonstrates wiring to a local service]   * [[/TwoComponents|Demonstrates wiring to a local service]]
Line 80: Line 80:
  * [wiki:/Calculator Calculator sample demonstrates wiring to several references]   * [[/Calculator|Calculator sample demonstrates wiring to several references]]
Line 84: Line 84:
  * [wiki:/EagerInit How an application can tell it is now running]   * [[/EagerInit|How an application can tell it is now running]]
Line 92: Line 92:
  * [wiki:/DeploymentSupport Deployment and launcher scenarios ]   * [[/DeploymentSupport|Deployment and launcher scenarios ]]
Line 94: Line 94:
  * [wiki:/ConversationalSupport Non-blocking/Conversations ]   * [[/ConversationalSupport|Non-blocking/Conversations ]]
Line 96: Line 96:
  * [wiki:/ExtensionDependencyManagement Extension dependency management ]   * [[/ExtensionDependencyManagement|Extension dependency management ]]
Line 100: Line 100:
  * [wiki:/SpringSupport Support for Spring Composites ]   * [[/SpringSupport|Support for Spring Composites ]]
Line 102: Line 102:
  * [wiki:/RhinoSupport Support for the Rhino JavaScript container ]   * [[/RhinoSupport|Support for the Rhino JavaScript container ]]
Line 104: Line 104:
  * [wiki:/Groovy Support for the Groovy container ]   * [[/Groovy|Support for the Groovy container ]]
Line 108: Line 108:
  * [wiki:/SimpleContainer Simple container] demonstrates creating a simple extension for supporting Java POJO component types, designed for tutorials   * [[/SimpleContainer|Simple container]] demonstrates creating a simple extension for supporting Java POJO component types, designed for tutorials
Line 110: Line 110:
  * [wiki:/SimpleBinding Simple container] demonstrates creating a simple binding extension, designed for tutorials   * [[/SimpleBinding|Simple container]] demonstrates creating a simple binding extension, designed for tutorials
Line 115: Line 115:
  * [wiki:/CeltixSupport Support for using Celtix as a binding extension ]   * [[/CeltixSupport|Support for using Celtix as a binding extension ]]
Line 117: Line 117:
  * [wiki:/Axis2Support Support for using Axis2 as a binding extension ]   * [[/Axis2Support|Support for using Axis2 as a binding extension ]]
Line 119: Line 119:
  * [wiki:/JSON Support for using JSON as a binding extension ]   * [[/JSON|Support for using JSON as a binding extension ]]
Line 121: Line 121:
  * [wiki:/JMS Support for using JMS as a binding extension ]   * [[/JMS|Support for using JMS as a binding extension ]]
Line 123: Line 123:
  * [wiki:/JavaSpaces Support for using JavaSpaces as a binding extension ]   * [[/JavaSpaces|Support for using JavaSpaces as a binding extension ]]
Line 129: Line 129:
  * [wiki:/DataTransformation Databinding transformation ]   * [[/DataTransformation|Databinding transformation ]]
Line 131: Line 131:
  * [wiki:/PersistenceService Persistence service ]   * [[/PersistenceService|Persistence service ]]
Line 135: Line 135:
  * [wiki:/OSGiSupport Support for OSGi-based deployment ]   * [[/OSGiSupport|Support for OSGi-based deployment ]]

A compilation of use-case scenarios people are currently working on or think would be useful to have.

These are divided into two sections: end-to-end scenarios that relate to how people would use Tuscany, and technology scenarios that illustrate how to use a specific feature.

SL - To me the "end to end" scenarios section is not significantly different from the technology samples. I'm not saying I disagree with the intent but I would like to see us express the end to end scenarios in business problems that potential users would recognize,

Business Scenarios

These scenarios demonstrate the role of SCA in various different categories of IT solution.

Web2.0/Mashup

  • A web application that demonstrates flexible and speedy aggregation of features. Use SCA to present the aggregatable functions as services and also to pre-aggergate some services for convenience. Use bindings such as JSON for client access.

eBusiness

  • Banking (BigBank?) / Retail example of role SCA can play in a customer oriented web site.

Enterprise

  • A set of business level services that are expected to interact (or be orchestrated) across an SOA fabric, e.g. could be something like celtix providing the ESB type function but the emphasis here is process flows and services interacting across different runtimes.

Virtualisation

  • The use of services to virtualize processes or data. For example, we can have an SCA component implement a pseudo buisness process and have JMS bindings on the wires to the components implementing the process activities. Hence we can move runtimes about physically withough affecting the process.
  • Another take is to demonstrate our ability to redeploy components local / to remote without recoding.

Management

  • Wiring up WSDM/MUSE services to do something useful. Present a console for management status reporting? Or Demonstrate how we could use wiring to automate management processes.

Data Management

  • Use a wired series of SCA components in and ETL scenrario. Use the ability to rewire to change aspects of the process.
  • Data federation as a wired set of services.

Product

  • How an ISV can adopt SCA as the platform for product development. Using features of SCA to enable reconfiguration and extension of product that is ultimately shipped on to their customer.

Business Integration

  • Not sure about this one. SCA can certainly describe and compose the services of one organisation. If two parties in a
    • BI scenario want to take the SCA approach then potentially you could image using SCA to describe the aggregation of services into a cross orgranisational system.

Anti Scenarios

  • Areas that we wouldn't concentrate on Compute Intesive, Desktop Apps, Real Time, ?

End to end scenarios

These examples show end user experiences, such as accessing a service (or assembly) via JSF or API. The focus of these is to guide the user step by step through building an end to end application

Accessing a Service

Creating Components

Wiring

Component Lifecycle

Technology Scenarios

These scenarios show how to use specific pieces of technology within Tuscany and demonstrate the operation of the runtime and its extensions.

Core

Containers

Extensions

  • Simple container demonstrates creating a simple extension for supporting Java POJO component types, designed for tutorials

  • Simple container demonstrates creating a simple binding extension, designed for tutorials

Bindings

System Services

System services are extensions to the core runtime that provide functionality used by other extensions or serve as extension points themselves.

Host Containers

Tuscany/TuscanyJava/Scenarios (last edited 2009-09-20 22:49:02 by localhost)