
Chapter 3
JAIN SLEE Overview
3.1 Introduction
This chapter discusses key principles of the JAIN SLEE 1.0 specification architecture.
The SLEE architecture defines the component model for structuring application logic for communications applications as a
collection of reusable object-oriented components, and for assembling these components into high-level sophisticated services.
The SLEE architecture also defines the contract between these components and the SLEE container that will host these compo-
nents at run-time.
The SLEE specification supports the development of highly available and scalable distributed SLEE specification-compliant
application servers, yet does not mandate any particular implementation strategy. More importantly, applications may be
written once, and then deployed on any application server that implements the SLEE specification.
In addition to the application component model, the SLEE specification also defines the management interfaces used to ad-
minister the application server and the application components executing within the application server. It also defines a set of
standard facilities such as the Timer Facility, Alarm Facility, Trace Facility and Usage Facility.
The SLEE specification defines:
• The SLEE component model and how it supports event driven applications.
• How SLEE components can be composed and invoked.
• How provisioned data can be specified, externally managed and accessed by SLEE components.
• SLEE facilities.
• How external resources fit into the SLEE architecture and how SLEE applications interact with these resources.
• How events are routed to application components.
• The management interfaces of a SLEE.
• How applications are packaged for deployment into a SLEE.
The following sections discuss the central abstractions of the SLEE specification. For more detail about the concepts introduced
in this chapter please refer to the SLEE specification, available at
http://jcp.org/en/jsr/detail?id=22
.
3.2 Events and Event Types
An event typically represents an occurrence that requires application processing. It carries information that describes the
occurrence, such as the source of the event. An event may originate from a number of sources:
• An external resource such as a communications protocol stack.
8
Komentáře k této Příručce