TheJava Community Process (JCP), established in 1998, is a formal mechanism that enables interested parties to develop standard technical specifications for Java technology. Becoming a member of the JCP requires solid knowledge of the Java programming language, its specifications, and best practices in software development. Membership in the JCP involves a detailed review of the candidate's profile, including an assessment by current members. Typically, professionals are invited to join the JCP based on their contributions and reputation within the Java community.
Once invited, the new member undergoes an evaluation by the JCP Executive Committee, ensuring that they can effectively contribute to the Java Specification Requests (JSRs). These formal documents describe proposed specifications and technologies to be added to theJava platform. New members are encouraged to engage actively and play a crucial role in supporting the Java community and its releases. It is essential that members possess expertise and in-depth technical knowledge, combined with strong professional experience, to significantly contribute to the growth and usage of theJava language.
Membership for organizations and commercial entities requires annual fees, but it is free for individuals. JSRs undergo formal public reviews before becoming final, and the JCPExecutive Committee votes on their approval. A finalized JSR provides areference implementation, which is a free implementation of the technology in source code form, and a Technology Compatibility Kit to verify the API specification.
The JCP itself is described by a JSR. As of 2020[update], JSR 387 describes the current version (2.11) of the JCP.
There are hundreds of JSRs. Some of the more visible JSRs include:
The JCP's executive board has been characterized as a "rubber stamp organization" sinceOracle acquiredSun Microsystems (the original developer of theJava language).[9]
TheApache Software Foundation resigned its seat on the board in December 2010 becauseOracle was unwilling to license theTechnology Compatibility Kit for Apache's version of Java.[10]
Source:[11]
| Award | Nominee | Contributions | Details | JSR # | Win? |
|---|---|---|---|---|---|
| JCP Member/Participant of the Year | London Java Community andSouJava | "Adopt a JSR!" program | Supporting Java developers through the JCP. | Win! | |
| Stephen Colebourne | Date and timeAPI forJava. | Comprehensive and advanced. Tireless work. | 310 | ||
| Markus Eisele | Active work among theGermanJava community and in theJSR 342 Expert Group. | 342 | |||
| JUG Chennai | Becoming the most active JCP organization inIndia and a competitive service organization in the commercial marketplace. | ||||
| Werner Keil | Incredible energy and participation inseven JSRs as well as the Executive Committee. | ||||
| Antoine Sabot-Durand |
| ||||
| Outstanding Spec Lead | Victor Grazi, | Java Money & Currency API | Dedicated, focused expertise in solving issues representingmoney andcurrencies. | 354 | Win! |
| Michael Ernst | Annotations onJavaTypes | Level-headed approach; a great example of a well-run JSR. | 308 | ||
| Nigel Deakin, | Java Message Service 2.0 | Outstanding, thorough, and intelligent work keeping the JMS 2 EG open and moving forward at a great pace. | 343 | ||
| Pete Muir, | Contexts and Dependency Injection forJava EE 1.1 | Voluntarily upgrading to 2.8 in late 2011 and maintaining what were already transparent methods in running his Expert Group. | 346 | ||
| Most Significant JSR | Jitendra Kotamraju | API forJSON Processing | An important step in bringingJava into the world of the modern web. | 353 | |
| Victor Grazi, | Money andCurrencyAPI | New ways of handling monetary amounts andcurrency computations. Fixing criticalJava Number Format and Representationbugs beyond monetary values. | 354 | ||
| Mitch Upton | Java State Management | The potential to improve how Application Servers and Distributed Services are going to look in the near future as well as simplifying deployment inPaaS and Cloud environments. | 350 | ||
| Nigel Deakin | Java Message Service 2 | Modernize JMS at a rapid pace. | 343 | ||
| Patrick Curran | JCP.Next | Setting the direction and procedures for the next-generation JCP. | 348355358 | Win! |
| Platforms |
| _waving.svg) | |||||
|---|---|---|---|---|---|---|---|
| Technologies |
| ||||||
| History | |||||||
| JVM languages | |||||||
| Community |
| ||||||
| Hardware |
|  | ||||||
|---|---|---|---|---|---|---|---|---|
| Software | ||||||||
| Storage | ||||||||
| Performance | ||||||||
| Research | ||||||||
| Education | ||||||||
| Community |
| |||||||
| Acquisitions | ||||||||
| Slogans | ||||||||
