Oracle® Java Micro Edition Software Development Kit Developer's Guide Release 3.3 for NetBeans on Windows E24265-05 |
|
Previous |
Next |
The Oracle Java ME SDK supports many standard Application Programming Interfaces (APIs) defined through the Java Community Process (JCP) program. JCP APIs are often referred to as JSRs, named after the Java Specification Request process. JSRs that are not part of the platform are referred to as "optional packages."
The CLDC/MIDP platform is based on the Mobile Information Device Profile and Connected Limited Device Configuration (JSRs 118 and 139).
The IMP-NG platform is base on Information Module Profile - Next Generation (IMP-NG) (JSR 228).
See Table 15-1 for a full list of supported JCP APIs. The Oracle Java ME SDK provides documentation describing how certain APIs are implemented in the SDK. Many supported APIs do not require special implementation considerations, so they are not discussed in this help set. "Oracle APIs" describes Oracle APIs provided to support the IMP-NG platform.
For convenience the Javadocs that are the intellectual property of Oracle are in your installation's \docs
directory. The remainder can be downloaded from http://jcp.org
.
Table 15-1 Supported JCP APIs
JSR, API | Name, URL |
---|---|
JSR 75, PIM and File |
PDA Optional Packages for the J2ME Platform |
JSR 82, Bluetooth and OBEX |
Java APIs for Bluetooth |
JSR 118, MIDP 2.1 |
Mobile Information Device Profile |
JSR 135, MMAPI 1.1 |
Mobile Media API |
JSR 139, CLDC 1.1 |
Connected Limited Device Configuration |
JSR 172, Web Services |
J2ME Web Services Specification |
JSR 177, SATSA |
Security and Trust Services API for Java ME |
JSR 179, Location |
Location API for Java ME |
JSR 184, 3D Graphics |
Mobile 3D Graphics API for J2ME |
JSR 205, WMA 2.0 |
Wireless Messaging API |
JSR 209, AGUI 1.0 |
Advanced Graphics and User Interface Optional Package for the J2ME Platform |
JSR 211, CHAPI |
Content Handler API |
JSR 217, PBP 1.1 |
Personal Basis Profile 1.1 |
JSR 218, CDC 1.1 |
Connected Device Configuration 1.1 |
JSR 226, SVG |
Scalable 2D Vector Graphics API for J2ME |
JSR 228, IMP-NG |
Information Module Profile - Next Generation (IMP-NG) |
JSR 234, AMMS |
Advanced Multimedia Supplements |
JSR 239 |
Java Binding for OpenGL ES API |
JSR 256 |
Mobile Sensor API |
JSR 257 |
Contactless Communication API |
JSR 280, XML API |
XML API for Java ME |
The IMP-NG project type supports developing applications for the Oracle Java ME Embedded 3.3 runtime. The Java ME Embedded 3.3 runtime includes several standard JSR APIs and additional Oracle APIs for embedded use cases. These new APIs are:
The Device Access API provides interfaces and classes for communicating with and controlling peripheral devices.
The Logging API provides a lightweight and extensible framework based on the concepts of the java.util.logging package, enabling applications to log messages in a variety of formats and using custom handlers.
The AMS API provides an interface to the application management capabilities of the runtime to allow authorized applications to interact with and extend the application management system.
The AccessPoint API is an extension to the Generic Connection Framework and enables applications to select among multiple access points if the underlying platform provides more than one data access point.
The Javadocs for these APIs are in your installation's \docs
directory.