Posted by monsonhaefel
on December 2, 2003 at 10:21 PM PST
IBM and BEA are working within the JCP process - they need the JCP.
A Microsoft wonk asked me an interesting question yesterday: Will IBM and BEA make the Java Community Process obsolete? The impetus for this question was the recent release of three J2EE "specifications" by IBM and BEA, which you can review here . Rather than develop these specifications from scratch within the JCP process, as is done in many cases, IBM and BEA decided to propose three new JSRs (235 , 236 , and 237 ) based on specifications that they had already developed. Is this wrong? Does this approach circumvent the JCP Process? Will IBM and BEA make the JCP obsolete? The short answer is, "No".
The Java Community Process (JCP ) is designed to facilitate the creation of standard, vendor-agnostic Java technologies. This is my quick and dirty definition, the keys to which are the words "facilitate" and "vendor agnostic". The primary objective of the JCP is to provide a framework for defining Java standards. In most cases, an expert group develops the standards based on a set of objectives defined by the proposed JSR (Java Specification Request). In other words, usually the specification is grown from scratch under the auspicious of the JCP. This, however, is not a requirement. The actual specification can be grown from scratch (e.g. JSP, JSF, EJB, etc.), based on established non-JCP standards (e.g. CORBA, DOM, SAX, ext.), or an existing implementation or architecture as is the case here. It really doesn't matter very much as long as the JCP accepts the JSRs, approve their progression through community and public drafts, and endorses the final specifications. The bottom line is that the JCP is not supposed to stifle the development of specifications seeded outside of the process - to the contrary. If leading vendors want to hammer out the details before beginning a JSR, then so be it. Who cares how it got started?
Contrary to what my friend from Microsoft Land may say, the JCP is not doomed to obsolescence