OSGi DevCon 2008 Since its initial meeting in January, 2007 the OSGi Enterprise Expert Group has made significant progress in addressing enterprise requirements for OSGi software, such as including a Spring based component model, introducing J2EE modularity, adopting SCA intents and bindings, and configuring and discovering various types of distribution software. The EEG was formed to standardize the OSGi approach to such enterprise requirements as multi-JVM services, improved management, and enhanced qualities of service. In this short-talk, co-chairs Tim Diekmann and Eric Newcomer will give an overview of the current activities and the proposed timeline for revising the OSGi specification. This talk is part of the OSGi DevCon and assumes little previous knowledge of OSGi and therefore is also of interest for non-OSGi members.

1. © 2008 by Newcomer, Diekmann; made available under the EPL v1.0 | Date | Other Information, if necessary
Enterprise Expert Group Status Report
Eric Newcomer (IONA)
Tim Diekmann (Siemens Com)

2. Presentation Title | Presentation Subtitle | © 2008 by Eric Newcomer, Tim Diekmann; made available under the EPL v1.0
Agenda
• What is the Enterprise Expert Group?
• What did the EEG do last year?
• What is the plan of the EEG for this year?
• Q/A

3. Presentation Title | Presentation Subtitle | © 2008 by Eric Newcomer, Tim Diekmann; made available under the EPL v1.0
What is the Enterprise Expert Group?
• founded November 2006, members include IBM, Oracle, BEA,
ProSyst, IONA, Siemens, Makewave, SpringSource, Jayway,
RedHat, Richard Hall
• charter:
 “define the technical requirements and specifications to tailor and
extend the OSGi Service Platform to address information technology
software infrastructure use cases found in enterprise business
scenarios“
• home page: http://www.osgi.org/EEG/HomePage (public), https://
www.osgi.org/members/EEG/HomePage (members only)
• regular meetings, face-2-face every 2 months, phone calls once a
month

4. Presentation Title | Presentation Subtitle | © 2008 by Eric Newcomer, Tim Diekmann; made available under the EPL v1.0
What did the EEG do last year?
• work on RFPs:
 105 JMX Management of the OSGi Framework
 81 OSGi Integration of SCA (as part of RFC 119)
 100 Visibility Scoping Of Exported Packages moved to CPEG
 87 OSGi Management Object Model moved to REG
 90 Remote Management Architecture moved to REG
 97 Third Party Dependency Resolution Constraints moved to CPEG
 103 Class Loading Improvements moved to CPEG
 82 Framework State Management Enhancements moved to CPEG
 83 Classloading and Marshalling moved to CPEG
 80 Framework Booting moved to CPEG
• work on RFCs:
 124 Component Model for OSGi
 119 Distributed OSGi - External Services and Service Discovery
 122 Database Services
 120 Security Enhancements moved to CPEG

5. Presentation Title | Presentation Subtitle | © 2008 by Eric Newcomer, Tim Diekmann; made available under the EPL v1.0
What is the plan of the EEG for this year?
• current focus is on distributed OSGi, OSGi component model,
and database services. Changes to the OSGi core as a result of
the EEG work are transitioned to the CPEG, RFPs related to
management were transitioned to REG
• finish spec, RI, TCK on RFCs:
 124 (Component Model)
 119 (Distributed OSGi)
 122 (Database access)
• contribute to OSGi V.<next> specification targeted for the end of
2008
• continue work on RFPs and RFCs

6. Presentation Title | Presentation Subtitle | © 2008 by Eric Newcomer, Tim Diekmann; made available under the EPL v1.0
Q/A

7. Presentation Title | Presentation Subtitle | © 2008 by Eric Newcomer, Tim Diekmann; made available under the EPL v1.0
Q/A