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

Compare with Current View Page History

« Previous Version 14 Next »

Overview

please help complete this page. Add information and we'll clean it up and make it readable
TBD Add an overview of Java SCA. Explain the relationship between kernel and extensions

Would be good to have a table of all extensions and links to their specific pages here

How about information on integration with other projects

Tuscany SCA Java Sub-Project

The Java SCA sub-project aims to provide enterprise-grade service infrastructure based on SCA. Some of our principles include:

  • We are not a reference implementation but a community that seeks to innovate based on the tenets of SCA.
  • We build runtimes that are distributed under the Apache Software License.
  • We believe developing highly scalable service-based systems should be easier than it currently is.
  • We believe in providing users with flexibility and choice. We do not dictate programming models but support many. Our runtimes are designed to be highly extensible so users may customize them to fit their needs.
  • We provide frequent releases of our software so users can experience the newest features and have access to the latest bug fixes.

What's New

move this to what's new link
We are currently planning an alpha release of the latest kernel version with support for a subset of SCA 1.0 features. This is intended as a release for users to try new features introduced in the specifications, including:

  • A new assembly syntax
  • Autowire
  • Stateful conversations
  • The new Java API and Annotations

We have also extensively refactored the kernel for increased modularity, simplification, and support for federated deployment, which will be introduced in the release following the alpha. For full details, see the Release Notes.

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