previous next trail start tutorial home feedback openwings.org

Component Service APIs

The net.openwings.component.Component interface is the centerpiece of the service-based component architecture provided by Openwings. It abstracts away the details of using synchronous (method-based) and asynchronous (messaging or event-based) communication between components.

The Component interface is just one of two layers of interfaces for providing and using services in the Openwings Component Services API. The other layer is net.openwings.component.ComponentComplex. Each is intended to provide a different level of functionality, as we'll see later.

A static class called net.openwings.component.ComponentFactory contains methods for obtaining instances of classes implementing each of these interfaces.

Finally, UseServiceListener is another important piece of the component API. UseServiceListener is used by a component to register ongoing interest in a service. For example, listeners could be used to notify components of a significant change in a screen display.

Next: The Component Interface

back to top

Copyright 2002, General Dynamics Decision Systems. All rights reserved.

previous next trail start tutorial home feedback openwings.org