SCA/SDO go to OASIS
However, with the number of partners on the specifications growing to 18, they have recently announced that work on the specifications has been completed. Furthermore, rather than continue to work on these specifications behind closed doors, the authors also announced their intent to turn them over to OASIS for standardization, as well as to turn over the SDO 2.1 Java Specification to the JCP and restart JSR 235. BEA and IBM, the current co-spec leads for JSR 235, are working with Sun on a plan to resolve the current set of issues around JSR 235 and are committed to a solution that allows this work to be done in the JCP.
As the press release states:
The SCA and SDO specifications can help organizations to more easily create new and transform existing IT assets, enabling reusable services that may be rapidly assembled to meet changing business requirements. These specifications greatly reduce complexity associated with developing applications by providing a way to unify services regardless of programming language and deployment platform. Both are technologies designed to simplify the representation of business logic and business data. Early customers are already implementing and gaining value.
As seems usual these days, the specification authors chose to take the OASIS route towards standardization. Patrick Gannon, president and CEO of OASIS had this to say:
We applaud the Open SOA Collaboration for reaching this milestone and for choosing to take the next step and advance this important work through an open standards process. We look forward to furthering the evolution of SCA from specifications to standards and to promoting the broadest possible industry adoption through education and implementation efforts.
If previous OASIS efforts are anything to go by, don't expect a finished standard for about 12 months. These specifications are huge and unless the authors expect a rubberstamping excercise, the OASIS policy of allowing any and all comers to influence the evolution of specifications towards standards can lead to interesting (and long) debates in technical committees. Whether or not SCA/SDO continues to be seen as a threat to JEE, JBI and other technologies remains to be seen. The fact that Sun is now an author of these latest specifications and IBM/BEA are interested in working within the JCP on this effort indicates that some bridge building has been taking place. Or is it a case of "Keep your friends close but your enemies closer"?
JBI Overlap is minimal
Re: JBI Overlap is minimal
Re: JBI Overlap is minimal
Todd Montgomery Dec 19, 2014
Juergen Hoeller,Stéphane Nicoll Dec 18, 2014