Component Services provide the mechanism to publish services as well as discover and
use services that have been created and published by others. Component services can provide a
singular model for publishing services across the workgroup (using Jini technology), on
the Internet (using Web Services) or to handheld devices (using Bluetooth)
technology.
The component services are the primary abstraction that programmers use to access
Openwings services.
Key functionality for Component Services
- Provides the ability to provide, locate and use services, without being dependent on any
specific service location/lookup mechanisms (current planned mechanisms include Jini, UDDI
for web Services, and Bluetooth discovery protocols).
- Communications between components (and the definition of the service provided by a
component) is defined by its service API which is implemented as a Java Interface.
- Provides a Java-based Component API for protocol independent synchronous (pull) and
asynchronous (push) services.
- Provides runtime control of components.
- Supports the reporting the status of a given component.
- Dynamically retrieves environment settings via the use of policies.
Documentation and Tutorials
Component
Services Specification
Component
Services JavaDoc Documentation
Developing
Components Tutorial
