Re: [soa-iwg] ECF and SOA initiative

[Oliver Wolf <oliver.wolf@xxxxxxxxx>]

Title: Re: [soa-iwg] ECF and SOA initiative

Scott,

as we all know very well, SOA means different things to different people. While we all agree on the basic tenets of SOA (loose coupling, interoperability, reuse etc.), the technical approaches differ. The main drivers behind the SOA initiative come from an “enterprise SOA, web services, strong governance” kind of background, while ECF seems to be more on the “peer-to-peer, dynamic discovery, java remoting” side of things. That’s perfectly fine and we absolutely don’t want to exclude this part of the universe — it’s just not in the center of the IWG founding members’ attention. If you, or the ECF project for that matter, wish to extend the roadmap AND commit to deliver, feel free to do so. That’s why we’ve put the draft version up for public discussion.    

BTW, in my opinion, SCA and RFC119 are not mutually exclusive. RFC119 could be a good way to implement the SCA wire in OSGi-based SCA runtimes, for instance.

Cheers,
Oliver

> > > Hi Ricco,
> > >
> > > RE: the proposed roadmap: I'm a little surprised that there doesn't seem 
> > > to be any mention of OSGi standards work on distribution/remoting (i.e. 
> > > RFC119) and the associated Runtime project work (i.e. Equinox and ECF) 
> > > on implementing those OSGi 4.2 specs.
> > >
> > > Things like service registrys, brokers, esbs/messaging, etc are 
> > > certainly mentioned in the roadmap, but there isn't any connection (that 
> > > I can detect) to whats going on in the OSGi standardization world in 
> > > terms of specification (OSGi 4.2/Service Registry/RFC 119) or Equinox 
> > > implemention of specs (in ECF 3.0 and beyond).
> > >
> > > OSGi services, remoting, distribution, discovery, messaging is where ECF 
> > > is focusing it's attention WRT service-oriented architecture, and this 
> > > roadmap doesn't have anything about those (OSGi/Equinox) pieces at all 
> > > as far as I can tell. This seems like a large omission to me.
> > >
> > > I understand the desire to stick closely to SCA (for example), but it's 
> > > pretty clear (to me at least) that OSGi 4.2/RFC119 is going to be an 
> > > important way forward into SOA for OSGi-based runtimes...and so it seems 
> > > to me that a reasonably comprehensive SOA initiative at the Eclipse 
> > > Foundation would want to include that. Is that incorrect?
> > >
> > > Scott
> > >
> > >
> > > Ricco Deutscher wrote:
> > > > Scott,
> > > >
> > > > Would it be possible to refocus the discussion to the actual SOA content?
> > > > I’d love to get your feedback to the proposed roadmap.
> > > > Especially I would like to hear from you what ECF could bring to the 
> > > > table.
> > > >
> > > > Please find attached the latest version 0.3 from Zsolt including the 
> > > > Guiding Principles for the roadmap the group agreed upon.
> > > >
> > > > Best,
> > > > Ricco
> > > >
> > > > ------------------------------------------------------------------------
> > > >
> > > > _______________________________________________
> > > > soa-iwg mailing list
> > > > soa-iwg@xxxxxxxxxxx
> > > > > https://dev.eclipse.org/mailman/listinfo/soa-iwg
> > > > >
> > > > > _______________________________________________
> > > > > soa-iwg mailing list
> > > > > soa-iwg@xxxxxxxxxxx
> > > > > https://dev.eclipse.org/mailman/listinfo/soa-iwg

Oliver Wolf
Lead Architect Runtime Platform
Tel.:    +49 228-182 19059
Fax:    +49 228-182 19193
Mobil:  +49 160-98931313
oliver.wolf@xxxxxxxxx
 
SOPERA GmbH - Open Source SOA
Subscription Services, Support & Maintenance, Training, 
Technical SOA Consulting & Customized Development
www.sopera.de <http://www.sopera.de/> 
 
SOPERA GmbH · Geschäftsführer: Dr. Ricco Deutscher, Harald Weimer, Peter Spiegel
Sträßchensweg 10 · 53113 Bonn · Handelsregister: Bonn HRB 15336
Hohenlindnerstraße 11b · 85622 München
 
 
Vertraulichkeitshinweis: Diese Nachricht und jeder übermittelte Anhang beinhaltet vertrauliche Informationen und ist nur für die Personen oder das Unternehmen bestimmt, an welche sie tatsächlich gerichtet ist. Sollten Sie nicht der Bestimmungsempfänger sein, weisen wir Sie darauf hin, dass die Verbreitung, das (auch teilweise) Kopieren sowie der Gebrauch der empfangenen E-Mail und der darin enthaltenen Informationen gesetzlich verboten ist und gegebenenfalls Schadensersatzpflichten auslösen kann. Sollten Sie diese Nachricht aufgrund eines Übermittlungsfehlers erhalten haben, bitten wir Sie, den Sender unverzüglich hiervon in Kenntnis zu setzen.