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
Typical usage patterns and message types
message transformation
multiple providers
multiple clients/hosts
RPC between SCA components
Basic RPC style operations between SCA components using the JMS binding.
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0" targetNamespace="http://sample" xmlns:sample="http://sample" name="HelloWorld"> <component name="HelloWorldClient"> <implementation.java class="helloworld.HelloWorldClient"/> <reference name="helloWorldRef"> <binding.jms uri="jms:HelloWorldService"/> </reference> </component> <component name="HelloWorldServiceComponent"> <implementation.java class="helloworld.HelloWorldServiceImpl" /> <service name="HelloWorldService"> <binding.jms /> </service> </component> </composite>
One component exposes a JMS service on a queue named 'HelloWorldService' (based on the service name). Another component invokes the service by sending JMS messages to that queue (based on the configuration in the binding.uri). With this configuration messages are marshalled into JMS messages as XML text messgages. After processing at the service a temporary destination is used for the response message. Again the response messages are marshalled into JMS messages as XML text messgages. Exceptions?
The sample helloworld-jms shows this scenario working in full.
Links to JIRA
Link to ML discussions
Asynchronous messages
Fire and forget
Pub sub messages
Alternative Message Types and transformation
Multiple Message Types
Callbacks and conversations
Referencing external JMS providers
Servicing external JMS providers
Alternative JMS providers?
Message priorities
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