Find JSRs
Submit this Search


Ad Banner
 
 
 
 

 

The 8th JCP Annual Awards Nominations

The dynamic, agile nature of the Java Community Process (JCP) program entails an ongoing reassessment of all activities and traditions. As usual, the community participated in nominating candidates for several awards related to efforts in 2010. However, this year's roster of awards reflects the Program Management Office (PMO) decision to combine the original six categories into a streamlined list of three: JCP Member of the Year, Outstanding Spec Lead, and Most Innovative Java Specification Request (JSR).

Winners in each category will be announced on September 22 at the Wednesday evening JCP community event held during the JavaOne 2010 conference. Winners and nominees are included permanently in the JCP program's hall of fame.

Meanwhile, the community applauds all of the award nominees, for all of their work with the community, Java Standard Edition (SE), Java Enterprise Edition (EE), or Java Micro Edition (ME). Each nominee, introduced below, has earned the community's recognition and respect.

Read the Awards Winners Press Release here ...

 
JCP Member/Participant of the Year
  • Aplix. * Winner * For leadership in the Java ME space.
  • Stephen Colebourne. Not only with JSR 310, but also in other areas, especially language improvements or Dynamic Languages on the JVM he continues his aim to help Java grow and mature.
  • Bob Lee/Google. Mainly for JSR 330.
  • Red Hat Middleware. For adapting JSR 330 into JSR 299. Despite a relatively tiny piece of software (JSR 330), it is a first step towards creating standards together with other companies instead of just following their own agenda ;-).
Outstanding Spec Lead
  • Emmanuel Bernard (Red Hat), JSR 303, Bean Validation. Emmanuel ran one of the most open specifications in the JCP history, maintaining a public specification document, public forum discussions, public issue tracker and an Apache-licensed TCK and RI. He also demonstrated unparalled collaboration with other JSR groups. But his most notable contribution was his first, reviving a staled specification and taking over leadership from another party.
  • Gavin King (Red Hat), JSR 299, Contexts and Dependency Injection for the Java EE Platform. The role of a Spec Lead is not an easy one, but this specification took the challenge to a whole new level. What started out as an effort to integrate the JSF and EJB technologies became a specification that would stimulate a commitment to collaboration across the EE platform.
  • Dave Kim (SK Telecom), JSR 327, Dynamic Contents Delivery Service API for Java ME.
  • Ronald Tögl * Winner *, JSR 321, Trusted Computing API for Java. With his passion and continuous effort he not only brought JSR 321 to EDR stage despite a more than challenging time. He also inspired companies to adopt the JSR and implement against it already.
Most Innovative JSR
  • JSR 309, Media Server Control API.
  • JSR 299, Contexts and Dependency Injection for the Java EE platform. Critics have foreshadowed the death of the Java language, claiming that there is little more than can be done to evolve it and therefore needs to be replaced. There have been similar claims that Java EE is becoming a legacy platform because it's not flexible enough to be extended. JSR 299 silenced these viewpoints.
  • JSR 331, Constraint Programming. * Winner * This JSR represents the real innovation in SE/EE since the 300 number of JSRs started; where almost every other JSR especially in SE/EE is just an upgrade to existing technologies.
  • JSR 327, Dynamic Contents Delivery Service API for Java ME.

 
 
Description of the JCP Award Categories

JCP Member/Participant Of The Year - This award recognizes the corporate or individual member (either Member or Participant) who has made the most significant positive impact on the community in the past year. Leadership, investment in the community, and innovation are some of the qualities that EC Members look for in voting for this award.
 
Outstanding Spec Lead - The role of Spec Lead is not an easy one, and the person who takes that responsibility must be, among other things, technically savvy, able to build consensus in spite of diverse corporate goals, and focused on efficiency and execution. This award recognizes the person who has brought together these qualities the best in the past year, in leading a JSR for the Java community (Java SE, Java EE or Java ME).
 
Most Innovative JSR - Innovation is key to the success of the JCP program and helps ensure we remain a fresh and vibrant community. This award recognizes the Spec Lead and Expert Group that have introduced the most innovative new JSR for the Java community (Java SE, Java EE or Java ME) in the past year.
 
   


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 

Nominee Profiles

JCP Member/Participant of the year

Aplix

Aplix Corporation sells the JBlend Java platform, a component, modular Java platform that is customized according to original equipment manufacturer (OEM) specifications. Aplix has shipped Java technology in 600 million of the mobile phones and other consumer electronics devices of more than 50 companies worldwide. Founded in 1986, the company has been a Sun Java licensee since 1996. Aplix cooperates with leading operators and industry groups such as the Blu-ray Disc Association, LiMo Foundation, Symbian Foundation, JCP program, and so on, in order to propel the enhancement, standardization, and adoption of Java ME technology. Within the JCP program, Aplix serves on the ME Executive Committee, is Maintenance Lead of JSRs 82, 118, 135, and 271, and has participated in the development of more than 15 ME JSRs. In particular, Aplix is focused on bringing the next generation of Java ME -- JSR 271, Mobile Information Device Profile 3 (MIDP3) -- to market.



Stephen Colebourne

Stephen Colebourne is a Java Champion employed as a member of technical staff with OpenGamma. As such, he is deeply involved in building a new platform for the finance industry, based on open-architecture and open-source with a focus on risk management. OpenGamma partly support his work as co-Spec Lead of JSR 310, Date and Time API. This JSR is a ground-up redevelopment of the date and time features in Java, including type-safe representations of major concepts like dates, time, months, periods and durations, as well as interoperation with common technologies such as XML and JDBC. Advanced features will provide Coordinated Universal Time (UTC) leap second support and full management of time zone rules. The specification, Reference Implementation (RI), and Technology Compatibility Kit (TCK) are being developed in an open manner at https://jsr-310.dev.java.net/. Stephen is also valued for his contributions to Java language improvements where he co-wrote the middle-ground FCM closures proposal and provided the Kijaro workspace for anyone to hack the OpenJDK to add an experimental language feature. He has contributed to many core libraries, including Joda-Time (the forerunner of JSR 310), other Joda projects (money, convert, properties, beans), and Apache Commons. Through his blog he has contributed to the debate on the future of the JCP program, at times acting as an investigative journalist. Stephen has two talks at JavaOne as part of a busy speaking calendar.



Bob Lee

As a Google employee, Bob Lee led the core library development for Android, created the Jolt award-winning Guice framework, served as Spec Lead for JSR 330, Dependency Injection for Java, represented Google on the JCP SE/EE Executive Committee, and contributed significantly to several Java 7 language changes. In a little over four months, JSR 330 whipped through all the stages to achieve final release October 2009, making it the most expeditiously completed spec in the history of the JCP program. JSR 330 has been a welcome contribution to the industry because it specifies a means for obtaining objects in such a way as to maximize reusability, testability, and maintainability compared to traditional approaches such as constructors, factories, and service locators. The speed of JSR 330's adoption has rivaled that of its development. Spring and Guice implement JSR 330, and JSR 299 extends it. Bob Lee (http://crazybob.org/) has since migrated to Square, where he currently leads engineering. He continues participating in the JCP community as an individual member.



Red Hat Middleware

In keeping with its commitment to develop software that is compliant with all relevant standards, Red Hat Middleware LLC joined the JCP program in September 2003. Red Hat believes standards must be developed in an open manner, with strong community participation. Red Hat lives up to that premise, with energetic involvement in the development of approximately 25 JSRs, addressing a wide range of technologies that belong to the Java EE and Java SE platforms. Red Hat helps facilitate the vigorous developer and user feedback that is critical to the continued success of the JCP program. One specific example of Red Hat's willingness to collaborate with other companies occurred when Gavin King, the Red Hat Spec Lead for JSR 299, Contexts and Dependency Injection for the Java EE platform, helped bridge the worlds of Java SE and Java EE by producing a specification that integrates formally disparate technologies, including Java EE 6, the JSR 330 API, Enterprise JavaBeans 3.1, and JavaServer Faces 2.0.



. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 


Outstanding Spec Lead

Emmanuel Bernard

Emmanuel Bernard is Spec Lead for JSR 303, Bean Validation, which he took over and revived from stagnation. This JSR is considered one of the most openly developed specifications in JCP program history in that Emmanuel maintained a public specification document, public forum discussions, public issue tracker, and an Apache-licensed Technology Compatibility Kit (TCK) and Reference Implementation (RI). He also collaborated diligently and diplomatically with other JSR groups to attain tight integration within the Java SE and EE platform. As a result, JSR 303 not only made it into the Java EE 6 specification, but it has had a profound influence on simplifying and centralizing validation across all the layers of an application, making it simpler, more consistent, and more robust. Emmanuel also serves as an Expert Group member for JSR 317, Java Persistence 2.0. He is lead developer on the Hibernate team and platform architect at JBoss by Red Hat, and co-authored the book Hibernate Search in Action. He speaks regularly at various Java User Groups (JUGs) and conferences, including JavaOne, JBoss World, and Devoxx, and he blogs and tweets extensively.



Gavin King

Gavin King is a fellow at JBoss, a division of Red Hat. He is the architect of Hibernate, an open source Object Relational Mapping (ORM) tool for Java, and of Seam, an open source application framework for Java EE. He has co-authored three books: Hibernate In Action (2004), Java Persistence with Hibernate (2006), and NHibernate in Action (2009). Gavin was Spec Lead of JSR 299, Contexts and Dependency Injection for the Java EE platform, which defines a standard dependency injection solution that combines the best features of several popular open source technologies. The ultimate goal of the project was to dramatically simplify the programming model for web-based applications written in the Java language. Gavin's collaboration with other JSR efforts improved platform harmony, catalyzed two new specifications (the Managed Bean Specification and the Interceptors Specification), and aligned JSR 299 with other technologies including JSR 330, Enterprise JavaBeans, JavaServer Faces, and JSR 303. Gavin speaks about JSR 299 at events such as JavaOne, JBossWorld, and JUG meetings and for prominent news sites such as InfoQ and DZone. He continues to work with other implementations, such as OpenWebBeans and Resin, to explain and promote the specification.



Dave Kim

Dave Kim has demonstrated agility in his Spec Leadership of the near-final JSR 327, Dynamic Contents Delivery Service API for Java ME, as well as his previous two-year effort, JSR 298, Telematics API for Java ME. He is the Business Development Director at SK Telecom International, a South Korean mobile telecommunications operator that is controlled by the SK Group, one of the country's largest business conglomerates. Dave also represents SK Telecom on the ME Executive Committee. His current JCP project, JSR 327, will enable Java applications to interact with dynamic content delivery (DCD) client implementations in mobile consumer devices.



Ronald Tögl

Ronald Toegl, Spec Lead for JSR 321, Trusted Computing API for Java, has a passion and drive that have enabled him to bring JSR 321 to the Early Draft Review (EDR) stage despite challenges outside of his control. Even at this early stage, he has inspired companies to adopt and implement the JSR. Ronald and his Expert Group, which includes academicians and individual members, are fully committed to developing the standard with as much transparency as possible. The JSR 321 page on the jcp.org site propels readers to a second website at java.net, where people can participate in the development and access the latest drafts of the source code. As a research assistant in the Trusted Computing Labs, Ronald is employed by IAIK of Graz University of Technology. His research interests include IP-based communications, formal methods in security APIs, and protocols for Trusted Computing. His work has been published as proceedings of numerous professional conferences such as the International Symposium on Trusted Computing (TrustCom), in articles of journals including ENISA Quarterly, and through presentations all over the world (Austria, Germany, Hungary, China, Korea, and the United States).



. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



Most Innovative JSR

JSR 309, Media Server Control API

JSR 309, Media Server Control API, standardizes an Application Programming Interface that enables the development and deployment of new media-rich applications for the Java platform. This API is for use with the modern IP- and SIP-based media servers that are becoming essential for many of today's communications applications and that offer functions such as Intelligent Voice Response (IVR), voice/video conferencing and mixing, speech recognition, and text-to-speech services. Typical end-user services built upon these functions are Voicemail, Conferencing, Call Center, and Telephone Banking. This API also frees developers from knowledge of the underlying media server control protocols, works seamlessly with JSR 289 SIP Servlet API, simplifies their work, and allows them to focus on the rich media applications. Furthermore, the applications will be interoperable across a variety of protocols and media servers, resulting in a wider market reach for Java platform media applications. JSR 309 is a new style of JSR -- not just a bottom-up protocol driver, but a high-level API built top-down with a domain abstraction based on a study of rich-media application use-cases. The co-Spec Leads for this project are Marc Brandt of Hewlett Packard and Tomas Ericson of Oracle.



JSR 299, Contexts and Dependency Injection for the Java EE platform

JSR 299, Contexts and Dependency Injection for the Java EE platform, was started mid-2006 by Spec Lead Gavin King of Red Hat Middleware LLC. Its release repudiates concerns that Java EE was not flexible enough to be extended. The JSR 299 Expert Group developed a programming model that combines the best of Jboss Seam, Google Guice, and Java EE, simplifies the programming model for web-based applications written in the Java language, and lays the foundation for a more consistent and better integrated EE platform. JSR 299's innovations include a novel use of annotations to improve the typesafety of Java code, and provision of an SPI (Service Provider Interface) for portable extensions to the Java EE platform. JSR 299 catalyzed the development of a unified notion of a Java EE component, which was eventually codified in the new Managed Bean specification. The Reference Implementation (RI) and Technology Compatibility Kit (TCK) for JSR 299 were released under open source licenses, a first for Java EE platform technology.



JSR 331, Constraint Programming

Constraint Programming (CP) is a proven problem solving technique with great practical applications in scheduling, resource allocation, configuration, and other areas. However, this powerful technology for years remained a prerogative of CP gurus. The objective of JSR 331, Constraint Programming API, is to make CP technology more accessible for business software developers by defining unified business interfaces for modeling and solving real-world constraint satisfaction and optimization problems. Having these unified interfaces will allow commercial application developers to model their problems in such a way that the same model can be executed with different CP Solvers without any changes in the problem representation. This will minimize vendor dependence without limiting vendor innovation, while helping bring the latest research results to practical business applications. Dr. Jacob Feldman, a CTO at OpenRules, Inc. and a senior research fellow at 4C, is the Spec Lead for this JSR. Related links:



JSR 327, Dynamic Contents Delivery Service API for Java ME

JSR 327, Dynamic Contents Delivery Service API for Java ME, is an optional package for Java ME enabled devices. The Application Programming Interface (API) provides three things. First, push-based content delivery facilitates the periodic delivery of customized content. Second, a uniform delivery mechanism works with a variety of network-enabled Java applications, regardless of data type or format. Third, a single point-to-point channel and/or broadcast communication for network-enabled applications uses currently available data transfer protocols such as HTTP, HTTPS, or SMS. Dave Kim of SK Telecom is the Spec Lead for this project.



. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .