Versions Compared

Old Version 17

changes.mady.by.user Simon Laws

Saved on

compared with

New Version Current

changes.mady.by.user Daniel Becker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

extensions

reference

service

properties

conversation

callback

OneWay

CallableRef

sec

txn

implementation-bpel-ode

(question) (error)

(tick) (question)

(error)

(error)

(error)

(error)

N/A

(error)

(error)

implementation-ejb

(tick)

(error)

(question)

(error)

(error)

(error)

(error)

(error)

(error)

implementation-java

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(question)

(error)

implementation-notification

(question)

(question)

(question)

(question)

(question)

(question)

(question)

(error)

(error)

implementation-osgi

(question)

(question)

(question)

(question)

(question)

(question)

(question)

(error)

(error)

implementation-resource

(error)

(tick) (error)

N/A

N/A

N/A

N/A

N/A

(error)

(error)

implementation-script

(tick)

(tick)

(tick)

(error)

(error)

(error) (tick)

(question) (error)

(error)

(error)

implementation-spring

(tick)

(tick)

(tick)

(error)

(error)

(error) (tick)

(question) (error)

(error)

(error)

implementation-web

(question)

(question)

(question)

(question)

(question)

(question)

(question)

(error)

(error)

implementation-widget

(tick)

(tick)

(question)

(error)

(error)

N/A

N/A

(error)

(error)

implementation-xquery

(tick)

(tick)

(question)

(error)

(error)

(error)

(error)

(error)

(error)

extensions

reference

service properties

conversation

callback

Targetable

Local Wire

data-api

OneWay

PassByRef

sec ctxt

txn ctxt

binding-atom-abdera

(tick)

(tick)

N/A

N/A

(tick)

(tick)

(tick)

N/A

N/A

(error)

(error)

binding-corba

(tick)

(tick)

(error)

(error)

(question)

(tick)

N/A

(error)

N/A

(error)

(error)

binding-dwr

(error)

(tick)

(error)

(error)

N/A

N/A

N/A

N/A

N/A

(error)

(error)

binding-ejb binding-feed

(tick)

(error)

(error)

(error)

(error)

(error)

N/A

(tick)

N/A

(error)

(error)

binding-gdata

(tick)

N/A

N/A

N/A

N/A

N/A

(tick)

N/A

(error) set Y?

(error)

(error)

binding-http

(error)

(tick)

N/A

N/A

N/A

(error)

(tick)

N/A

N/A

(error)

(error)

binding-jms

(tick)

(tick)

(tick)

(tick)

(question)

(tick)

N/A

(tick)

(error) set Y?

(error)

(error)

binding-jsonrpc

(error)

(tick)

(error)

(error)

(error)

(error)

N/A

(error)

N/A

(error)

(error)

binding-notification

(question)

(question)

(question)

(question)

(question)

(question)

N/A

(question)

(question)

(question)

(question)

binding-rmi

(tick)

(tick)

(error)

(error)

(question)

(tick)

N/A

(question)

Y

(error)

(error)

binding-rss-rome

(tick)

(tick)

N/A

N/A

(tick)

(tick)

(tick)

N/A

N/A

(error)

(error)

binding-sca

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

N/A

(error)

Y

(tick)

(error)

binding-sca-axis2

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

N/A

(error)

(question)

(tick)

(error)

binding-sca-corba binding-sca-xml

(question)

(question)

(question)

(question)

(question)

(question)

N/A

(question)

(question)

(error)

(error)

binding-ws-axis2

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

N/A

(tick)

(error) set Y?

(tick)

(error)

Tuscany Feature Driven Scenarios (itest)

See ...

Some links to scenarios we already have spread around the place. I'd like to see us migrate the scenarios that work into the user guide and those are a requirement and are outstanding should become wish JIRA.

Web2.0 Scenarios java roadmap http://tuscany.apache.org/sca-java-roadmap.html databinding scenarios Databinding Scope

JMS

...

...

...

Spring Scenarios Spring Scenarios
Databinding scenarios Databinding Scope
Policy Model ScenariosPolicy Model Scenarios
Policy Security Scenarios Policy
Policy Definitions Scenarios http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+definitions.xml
JMS Scenarios JMS Scenarios

RPC between SCA components

Basic RPC style operations between SCA components using the JMS binding.

Code Block

<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)

...