THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
SCA Assembly Spec Driven Scenarios (vtest)
extensions |
reference |
service |
properties |
conversation |
callback |
|---|---|---|---|---|---|
implementation-bpel-ode |
|||||
implementation-ejb |
|||||
implementation-java |
|||||
implementation-notification |
|||||
implementation-osgi |
|||||
implementation-resource |
|||||
implementation-script |
|||||
implementation-spring |
|||||
implementation-web |
|||||
implementation-widget |
|||||
implementation-xquery |
|||||
binding-atom-abdera |
|||||
binding-corba |
|||||
binding-dwr |
|||||
binding-ejb |
|||||
binding-feed |
|||||
binding-gdata |
|||||
binding-http |
|||||
binding-jms |
|||||
binding-jsonrpc |
|||||
binding-notification |
|||||
binding-rmi |
|||||
binding-rss |
|||||
binding-sca |
|||||
binding-sca-axis2 |
|||||
binding-sca-corba |
|||||
binding-sca-xml |
|||||
binding-ws-axis2 |
Tuscany Feature Driven Scenarios (itest)
See ...
java roadmap http://tuscany.apache.org/sca-java-roadmap.html
databinding scenarios Databinding Scope
JMS
Current user guide describes some ways to use it http://tuscany.apache.org/sca-java-bindingjms.html
want to describe where the JMS binding is going
multiple providers
multiple clients/hosts
Spring
Working with different bindings
policy/transaction/security
Component type with service, reference, property derived from the spring implementation
The development cycle.
User Level Scenarios (itest/demo/tutorial)
Building a stand alone service
Building a stand alone web app
Integration with Web2.0 style UI
Aggregate multiple services into new ones
Integration with existing, non-sca, services
Reusing services
Rewiring services
Integration with non Java SCA runtimes.
A statically configured distributed application as an SOA
Starting and stopping parts of an SOA
Secure messaging between selected services
Mediation and routing between services
Balance load across multiple identical running services
Tolerate service failure