Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [soa-iwg] Request to include ECF in the Eclipse SOA package for Helios
I want to clarify this request a little bit, as it's a little unclear from Oliver's email what we are actually requesting be included in this package.
We are not requesting to include *all* of ECF in the soa package...since ECF includes a number of APIs, example apps, and tools...not all of which are relevant to the soa package.
Rather, we are specifically requesting that the SOA runtime package include our implementation of the OSGi 4.2 remote services specification...which is currently the only standard for service-oriented architecture in OSGi runtimes. Some of the technical characteristics of this implementation are described here [1].
ECF's transport-independent implementation of OSGi 4.2 specification already has the basic runtime support for integration with soap and rest-based tooling [2]. We certainly will work collaboratively with the Swordfish and/or other teams to support other tooling and runtime components and look forward to doing so. For example, through community contributions we have already done this with SpringSource's runtime components and tooling [3].
If there are any other technical, releng, and/or integration questions regarding this request, please make them known here. 

Scott
[1] http://eclipseecf.blogspot.com/2010/01/osgi-remote-services-from-ecf.html http://wiki.eclipse.org/ECF [2] http://eclipseecf.blogspot.com/2010/01/soap-rest-and-ecf-remote-services.html [3] http://eclipseecf.blogspot.com/2010/02/goodness-through-osgi-standards.html 


Oliver Wolf wrote:

Hi,
there has been a request from one of this IWG's participants, Scott Lewis, to consider the work done by the ECF for inclusion in the Helios release of the Eclipse SOA package.
From a purely technical point of view, the SOA runtime technology (Swordfish) already available in the Eclipse SOA package is mostly complementary to ECF. IIRC, there was agreement that a tighter integration between Swordfish and ECF would be beneficial, but is not absolutely required (again from a technical point of view) since both Swordfish and ECF can be used independently and appeal to different target audiences. Moreover, none of the SOA IWG's participants seems to be ready for investing the required effort at his point. The SOA IWG charter, however, states as one of the deliverables of the SOA IWG that
"It will define and maintain requirements and a roadmap that defines a SOA platform and encourage broader participation from different solution providers. All requirements are evaluated with respect to the overarching goal of providing an interoperable SOA Platform. Requirements to integrate with technologies that are not part of the SOA Platform are considered out of scope by the SOA IWG."
The question that arises here is IMO whether including ECF in the Eclipse SOA package contributes to meeting "the overarching goal of providing an interoperable SOA Platform" or not.
Frankly, I'm not sure how we should proceed now as per the IWG charter and the more general Eclipse Industry Working Group Process. FWIW, the IWG process states that "All Participants in an IWG, whether Steering Committee Participants or Member Participants, can participate and will have voting rights with respect to all IWG matters, including scheduling meetings and activities, and will have equal rights of access and participation in the development of all Materials, including Marketing Programs, Material development, mailing lists and wikis."
so I'd assume that we'd have to do a formal vote among the participants? @Don, can you advise? 
Regards,
Oliver


------------------------------------------------------------------------

_______________________________________________
soa-iwg mailing list
soa-iwg@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/soa-iwg

Back to the top