|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
Originally designed for the management of network-attached devices OSGi builds a de-facto standard to modularise all kinds of complex Java applications. It enables deployment and updating of components, which are called bundles, by supporting automatic resolution of inter-component dependencies. Despite these benefits the OSGi specification omits dedicated support for discovery, selection and loading of locally unavailable bundles. However, this is a key requirement for large distributed applications especially in dynamic and heterogeneous environments. Current solutions are server-based and provide a central bundle repository thereby representing a single point of failure. Furthermore, these approaches lack support for automatic bundle selection based on non-functional properties such as resource demand or performance. We introduce the D2CM infrastructure accounting these issues and enabling automatic discovery, selection and loading of bundles in a distributed system on basis of the peer-to-peer platform JXTA. By providing extended bundle descriptions, non-functional properties can be automatically evaluated for bundle selection and dependency resolution. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
Additional Classification:
Keywords:
Collaborative Colleagues:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||