| Overview |
| Architecture |
| Downloads |
Architecture
CoRE provides two sets of interfaces: Discovery interface to discover components, and Access interface to access components. The Discovery interface provides the functionality to discover a component by its keyword, by its URI, by its property, or by the input or output of its operation. The Access interface provides the functionality to invoke an operation of a component, and the functionality to retrieve a property of a component.
When initializing CoRE, one or more Engines can be plugged in under the Discovery or Access interfaces.
A DiscoveryEngine, an Engine for the Discovery interface, either bridges CoRE onto a repository service, such as UDDI, or implements a discovery mechanism, such as Gnutella protocol. A DiscoveryEngine incorporates a CoSMoS parser to convert the metadata (e.g. WSDL) of the discovered component into CoSMoS.
An InvokerEngine, an Engine for the Access interface, implements local or remote invocation of operations (i.e. methods) using a specific technology, such as CORBA, SOAP, or RMI.
A PropertyAccessEngine, another Engine for the Access interface, provides a mechanism to retrieve a property of a component through a specific technology, such as File search, WWW access, or database query.
We have implemented CoRE in Java. Currently, we have completed the implementation of CoRE's Engines for a local environment, i.e., the Engines to discover and access the components stored on a local host. The Engines using Web Service technologies are also under development.
@