You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 71 Next »

Unable to render {include} The included page could not be found.

Tuscany SCA Java

Tuscany Java SCA provides the infrastructure for easily developing and running applications using a service-oriented approach. This lightweight runtime is designed to be embedded in, or provisioned to, a number of different host environments without much effort. SCA Java is integrated with Tomcat, Jetty and Geronimo.

In Tuscany Java SCA, the SCA domain can run on a single JVM (Node) or it can run across multiple JVMs (Nodes) without modifying the way that each component is described. A domain is a logical concept that bounds all of the components within an application.

At the very high level, Java SCA can be divided into core and extensions. The core supports the SCA assembly model. The extensions provide Tuscany value-add features as well as extension point for runtime which enables any binding type, implementation types(programming model), policy and data binding to be easily added to it. The Tuscany community has contributed the extensions that are shown in the table below for SCA Java.

(lightbulb) Build your first SCA application in 10 minutes! Give it a try

Implementation Types

Bindings

Data Bindings

Interface Types

Java components
Spring assemblies
Scripting with JSR 223(JavaScript, Groovy, Ruby, Python & XSLT)
BPEL (a prototype using Apache ODE)
XQuery
OSGI

Webservice using Apache Axis2
JMS (tested with Apache ActiveMQ)
JSON-RPC
EJB
Atom/RSS

JAXB
SDO
Axiom
Castor
XMLBeans

Java
WSDL 1.1

To find out what we are working on in our 1.x and 2.x code bases see our Java SCA Roadmap Wiki Page

Copyright © 2006, The Apache Software Foundation Apache Tuscany is undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Web Services PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

  • No labels