On 5/4/07, Peter Neubauer <[EMAIL PROTECTED]> wrote:
Anyone else with more knowledge who can shed some light on this?
Essentially, OSGi Alliance Enterprise Expert Group (EEG) is currently in the process of collecting Request For Proposals (RFPs) which is a fairly open process to the general public. One such RFP being worked on is the Spring-OSGi integration, and I think several, if not majority, of the EEG participants are positive that this RFP will end up being the Spring-OSGi specification at some later point in time. In any event, and this is not an issue being brought forward at OSGi Alliance yet, I think that the EEG output will probably trigger the separation of the Core Platform EG (CPEG) releases from the other ones. That might mean that the EEG produces a set of specification prior to the CPEG's R5 release, if and when that comes out, or the other way around. And I doubt that Spring-OSGi integration work will become a CPEG concern, as it fits badly with the Mobile EG's requirement... But who knows at this point in time. What seems to be clear; Spring 2.1 will be "OSGi enabled", meaning that Spring beans will be seen as OSGi services and vice versa, by placing the bindings in the jar file. I think, but don't depend on it, that end of the day the same spec will be an important part of the EEG's set of specifications. Cheers Niclas
