This is important because according to OSGi Alliance rules, only members are allowed access to working drafts of documents. This is the first time we’ve released any of these drafts publicly. As a board member and EEG co-chair, I’m very pleased to see this happen because (a) I often get asked about what’s going on and why we can’t (in this age of open source) release details of what we’re doing and (b) I’m very interested in feedback from the broader OSGi community.
The enterprise edition activity started in January, 2007 with a review of requirements gathered at the enterprise workshop event. Following the OSGi Alliance process, the newly formed enterprise expert group members began writing Request for Proposal (RFP) documents. After an RFP on a particular topic is formally accepted, members can begin writing the Request for Comments (RFC) documents to design solutions to one or more of the RFPs. The early draft contains some of the RFCs that are far enough along to be released – in fact this represents a majority of current work items.
One major work item that is not far enough along, BTW, is the Java EE mapping to OSGi. (Not that I’m trying to put any pressure on any of the members of the group to hurry up and finish their work or anything 😉
The draft is divided into two major sections, like the work: Core and Enterprise (reflecting requirements taken on by the CPEG and EEG, respectively), pretty much (but not strictly) depending on whether the RFC affects the core, or something mapped to the core.
From here, the RFPs (which I call the design docs) are fed into the formal specification drafting process. So it is a great time to submit your comments (please be sure review the feedback form before you do – this basically defines the IP protections and rights involved).
Of course I am particularly interested in any feedback you may have on the distibuted OSGi document (RFC 119), but you may also be interested in:
- the Spring-DM inspired component model design (RFC 124)
- or some of the proposed security enhancements (RFC 120)
- the new command line capability (RFC 132)
- the new service registry hooks (RFC 126)
- the bundle tracker (RFCs 121 and 125)
- transaction support (RFC 98)
- or the DS updates (RFC 134)
It’s almost 300 pages, but there’s some good stuff there, and 18 months into the task, I think we have a pretty good handle on some things. But then again, maybe not…
The big new areas of course are the distributed OSGi and the “Spring-inspired” component model. And of course, as always, I am very interested in any comments or feedback about the suitability of the OSGi programming model for the enterprise, especially given some of these proposed enhancements.