| Osgi |
Articles about Osgi |
Information AboutOsgi |
| CATEGORIES ABOUT OSGI | |
| standards organizations | |
|
Over the past few years it has specified a , Configuration Management , Preferences, Http Service (runs Servlet s), XML parsing, Device Access, Package Admin, Permission Admin, Start Level, User Admin, IO Connector, Wire Admin, Jini , UPnP Exporter, Application Tracking, Signed Bundles, Declarative Services, Power Management, Device Management, Security Policies, Diagnostic/Monitoring and Framework Layering.
In the following more details about the history, the specification and the community acceptance are provided. SCOPE The Framework implements an elegant, complete, and dynamic Component Model - something that is missing in standalone Java/VM environments. Applications or components (coming in the form of Bundle s for deployment) can be remotely installed, started, stopped, updated and uninstalled without requiring a Reboot - management of Java Package s/ Class es is specified in great detail. Life Cycle Management is done via APIs which allow for remote Downloading of management policies. The Service Registry allows bundles to detect new Service s, or the going away of services, and adapt accordingly. The original focus was on . CLASSIFICATION: OSGI & SYSTEM-LAYERING SPECIFICATION PROCESS The OSGi specification is developed by the members in an open process and made available to the public free of charge and without s contains 10 companies. ORGANISATION The Alliance has been founded by Sun Microsystems , IBM , Ericsson and others in March 1999 (after it was first called the Connected Alliance). Among its members are (as of April 2006) more than 35 companies from quite different business areas, like for example . The Alliance has a Board of Directors for the respective working areas. For each area there also are so-called Officers. On the commercial side cooperation takes place in different comitees, while technical issues - like developing the specification further, from Release 1 over 2 and 3 to R4 - is handled by the existing Expert Groups. There are dedicated Expert Groups for the areas Mobile, Vehicle and Core Platform. COMMUNITY In October 2003, Nokia , Motorola , ProSyst and other OSGi members formed a Mobile Expert Group (MEG) that will specify a MIDP -based service platform for the next generation of smart mobile phones, addressing some of the needs that CLDC cannot manage - other than CDC . MEG became part of OSGi as with R4. Also in 2003 and Knopflerfish have Eclipse plug-ins available specifically for OSGi developers). There is a vibrant open source community revolving around the OSGi specifications. See Equinox OSGi , Apache Felix and Knopflerfish OSGi . NEWS IN OSGI RELEASE 4 The new features of OSGi R4 in brief are as follows (closely following the corresponding OSGi press release):
BLOGS
REFERENCES
GUIDANCE AND INFORMATION EXCHANGE
VENDORS AND IMPLEMENTATIONS
RELATED RFCS AND JAVA STANDARDS
RELATED TECHNOLOGY STANDARDS |
|
|