Welcome to the July edition of JSR Watch! Each month this column provides information about the JCP program: newly submitted JSRs, new draft specs, Java APIs that were finalized, and other news from the JCP program. This month's column discusses a set of new J2EE technology JSRs, and a scripting JSR, but I'll start off with the J2ME environment.
Two J2ME JSRs Are Nearly Final
JSR 179, Location API for J2ME technology, specifies how to write mobile location-based applications for devices with limited resources, producing information to an application about the device's physical location. This effort, led by Nokia, successfully navigated the final approval ballot on June 2, collecting 14 yes votes from the ME EC members. The second one is JSR 195, Information Module Profile. This JSR just posted its proposed final draft and is expected to enter the final approval ballot very shortly. Originally submitted in October of 2002, it has been moving through the community process at a very decent clip. The effort is closely related to MID-P in that it provides a Java runtime environment similar to MID-P but for devices that don't have graphical display capabilities. The JSR is co-led by Siemens and Nokia.
Ease of Development
If you attended this year's JavaOne conference, you'll have seen the above phrase featured in various technical sessions. It is also a topic that the Executive Committees are discussing at our monthly meetings, where it has the ominous title "Making Java more attractive." These meetings contemplate whether the community is developing the right technologies and the right tools, and has the needed developer programs to make Java developers more productive and significantly increase their number beyond the current three million. The JavaOne conference had several related announcements but I'll leave those to the marketing folks. The JCP already approved a few new JSRs that will help ease the complexity of development - such as JSRs 175, 181, 198, and 201. Now, four new JSRs related to J2EE technology have been added to the effort.
JSR 220 will define Enterprise JavaBeans version 3. The main scope is to reduce EJB's complexity from a developer point of view not only by making use of metadata annotations but also by providing utility classes, more programmatic defaults, simplification of stateless session beans, and much more. JSR 221, JDBC version 4, proposes to make use of new Java programming language features such as annotations and generics as well as provide sets of utility classes. JSR 222, the next version of the Java API for XML Data Binding, aims to complete the support for all W3C XML Schemas. This expert group is expected to work closely with the new JSR 224, JAX-RPC 2.0, expert group to establish better support for several XML Schema data types. JSR 222 also expects to define the mapping of Java to XML Schema (version 1 is already defined the other way). And, last, JSR 223, version 2 of JAX-RPC - this effort proposes to add support for the latest W3C and WS-I standards such as SOAP 1.2 and WSDL 1.2. This JSR will work closely with a number of others such as JSR 181 (Web Services Metadata) and JSR 173 (Streaming API for XML).
A Scripting JSR
JSR 223, Scripting Pages in Java Web applications, introduces the basic technical foundation to bridge the scripting community and the Java community. This addresses a need for application developers who use technologies like PHP, ECMAScript, and Active Server Pages by setting a standard mechanism with which you can access Java objects. These Java objects could be in a Java servlet container or in a Java VM. While PHP will be the expert group's first focus to provide a binding for, other scripting languages are considered as well. The Java Servlet Specification (JSR 154) defines abstractions for Web application context, request, response, and so on. When writing Web applications, Java classes and objects are developed that interact in well-defined security, resource, and class loader contexts. The JSR describes how this is exposed to scripting languages.
Fifteen ME EC Members?
Those of you who watch the ballot outcomes closely may have noticed that there are 15 voting ME EC members while there are 16 for SE/EE EC. Zucotto Wireless, which was elected to the ME EC in 2000 and reelected in 2001, has unfortunately closed its doors. Its seat will be vacant until the elections in November this year. Via this forum I would like to thank the folks of Zucotto for their hard work and contributions to the Java community and wish them well in their new adventures.
That's it for this month. I am very interested in your feedback. Please e-mail me with your comments, questions, and suggestions.
About The Author
Onno Kluyt is the director of the JCP Program Management Office, Sun Microsystems.