Though Sun Microsystems (www.sun.com) started the JCP and remains the dominant factor in the creation and approval of Java Specification Requests (JSR), a host of companies, organizations, and individuals also play a role. JSRs tend to gain approval only after months or even years of discussion, and the numbering convention, although sequential, only indicates when the process starts. For example, JSR-1, the Real-Time Specification for Java, will have production versions available only later this year. As Muksh Patel, president of hardware vendor Nazomi, notes, "JCP is time consuming, but it works." It allows companies like Nazomi to incorporate such features as multimedia support in a standard fashion. www.jcp.org
Key Embedded Java Standards | |
JSR | Description |
1 | Real-Time Specification for Java |
8 | Open Services Gateway Specification (OSGi) |
16 | J2EETM Connector Architecture |
19 | Enterprise JavaBeansTM 2.0 |
27 | Java Cryptography Extension 1.3 |
30 | J2ME Connected, Limited Device Configuration (CLDC) |
31 | XML Data Binding Specification |
36 | J2ME Connected Device Configuration (CDC) |
37 | Mobile Information Device Profile (MDIP) for the J2ME Platform |
46 | J2ME Foundation Profile |
54 | JDBC 3.0 Specification |
58 | Java 2 Platform, Enterprise Edition 1.3 Specification |
62 | Personal Profile Specification (for J2ME) |
68 | J2ME Platform Specification |
75 | PDA Profile for the J2ME Platform |
78 | RMI (Remote Method Invocation) Custom Remote References |
82 | Java APIs for Bluetooth |
99 | Java Specification Participation Agreement |
118 | Mobile Information Device Profile (MIDP) 2.0 (extends JSR-37) |
120 | Wireless Messaging API |
133 | Java Memory Model and Thread Specification Revision (proposed) |
134 | Java Game Profile |
135 | Mobile Media API |
169 | JDBC Optional Package for CDC/Foundation Profile (proposed) |
178 | Mobile Game API (for MDIP 1.0) |
189 | Java 3D API 1.4 |
190 | Event Tracking API for J2ME |
Comments
Comments