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

Compare with Current View Page History

« Previous Version 7 Next »

Overview

The SCA Java runtime is composed of a kernel and extensions. The kernel is essentially a multi-VM wiring engine that connects components together using the principles of Dependency Injection, or Inversion of Control.

The kernel is designed to be simple and limited in its capabilities: it wires functional units together. Capabilities such as service discovery, reliability, support for transport protocols, etc. are provided through extensions. The kernel extension model is based on the SCA 1.0 Java programming and assembly model. In otherwords, the kernel uses SCA to bootstrap itself. The mechanics of how this is done are described in detail elsewhere Kernel Architecture.

Extensions

The kernel is divided into a number of modules, among them spi and core. The spi module defines extension points and abstract helper classes. Extension types are not fixed and the kernel is designed to be as flexible as possible by providing an open-ended extension model. From the kernel perspective, extensions are just a set of SCA components. However, there are a number of known extension types defined by spi module, including:

  • Component implementation types, e.g. Spring, Groovy, and JavaScript
  • Binding types, e.g. Axis, CXF, AMQP, ActiveMQ, JXTA

There are also a number of add-on extensions that do not correspond to a well-know type:

  • The JPA extension for O/R mapping
  • The Geronimo Transaction Manager extension for transactional support in the runtime
  • The HOWL-based Persistent Store extension for high-throughput persistence of conversational state

More detail can be found in the Extensions Architecture section, but a few high-level best practices for designing extensions can be listed here:

  • Make sure you are familiar with SCA 1.0 Assembly and the SCA Java 1.0 programming model. Specifications can be found at www.osoa.org.
  • Never reference any classes in core. These classes are implementation-specific and subject to change; they are not part of the public SPI contract.
  • Use autowire when assembling extension components.

Federation

  • No labels