Page History

...

Tuscany SCA supports other modes of operation that will be of interest to Web2.0 application developers. For example, the Tuscany Java SCA Chat sample 8 provides binding.dwr to implement a Direct Web Remoting 9 connection between a Javascript browser based application and an SCA service. Using this binding, service to browser communication is supported alongside browser to service communication.

TODO - move policy stuff here.

Data integration - Raymond

...

Coming back to the business questions we discussed earlier in the paper your application development process will involve some of the following steps. The order of the steps here will vary of course as it is unlikely that you will be starting with a clean sheet.

Model the application in a ".composite" file.

• Identify what business functions are required and describe them using SCA Components and Services
• Identify what dependencies each component has and provide each component with suitable SCA References.
• Introduce SCA Properties for any values that will have to change as the application is reconfigured or redeployed.
• Compose the services within an SCA composite structure and connect references to services using Wires

Provide business logic

• Implement each component and reference the implementation from the component in the .composite file
• This implementation may simply wrap existing application logic.

Provide deployment specific information

• Describe any specific protocols that need to be used using bindings. References and Describe any specific protocols that need to be used using bindings. References and Services without bindings will adopt a default communication strategy

• Identify the components in you application and the services that these components provide
• Identify the services that these components depend on. These are the components references.
• Build an XML (.composite) file describing the components, services, references and the relationships between them
• Build the component implementations
• Contribute the .composite file, the component implemenations and any dependencies to the Tuscany SCA runtime.

• Attach organizational policy intents to the model, for example, security intents such as authorization or confidentiality

The application model and its component implementation dependencies can now be contributed to the Tuscany SCA runtimeThe order here varies as in may cases you may already have suitable component implementations that you just want to describe to Tuscany SCA.

Choosing how to run the Tuscany SCA runtime depends on you local environment but there are several options currently supported.

...