||PIM & File Data API
— Add Remove phone contacts
— Calandar events and recurring events
— File access, Secure Digital card, Memory Stick card
— Ringtone location is platform dependent – but
— No write access to system filesystem areas
— Search for Bluetooth devices
— Query device profiles and capabilities
— Open stream connection to device
||Mobile Information Device
Adds the following to MIDP1.0:
— UDP/Sockets/Secure Sockets/Server Sockets and access to
— Additional image formats (GIF / JPG / WMB)
— PCM (Pulse Code Modulation) wave format and/or additional
sampled/synthetic sound formats
— Copy protection of MIDlet suites
— Discovery/Installation of MIDlets via other mechanisms
— Custom 'built-from-scratch' UIs (e.g. www.thinlet.com)
||Wireless Messaging API 1.0
— Includes support for Short Message Service (SMS),
Supplementary Service Data (USSD) and Cell Broadcast Service (CBS)
— Push capabilities (launching a MIDlet on message receipt)
||Mobile Media API
— MMAPI provides support for accessing and controlling
time-based media such as audio and video
— MMAPI is a superset of MIDP 2.0 multimedia capabilities,
adding support for playback and capture of image and video
||Connected Limited Device
Add the following to CLDC 1.0:
— Floating point maths support
— Weak references support
||J2ME Web Services
The purpose of this specification is to define an optional package that
provides standard access from J2ME to web services.
||Security and Trust API
— Provides support for the management of user certificates
— Provides support for user authentication using certificates
— Allows for J2ME applications to communicate with
SmartCard-based applications and also to general purpose encryption
— Provides security through the addition of a Security
Element usable in operations
An Optional Package that enables developers to write mobile
location-based applications for resource-limited devices. The API works
on the J2ME CLDC v1.1 and CDC configurations.
SIP API for J2ME defines a multipurpose SIP API for J2ME clients. It
enables SIP applications to be executed in memory limited terminals,
especially targeting to mobile phones.
||Mobile 3D Graphics
— Provide an efficient 3D Graphics API suitable for the J2ME
platform (focused on CLDC/MIDP)
— Supports scene graph API (high-level) and immediate API
(low-level, subset of OpenGL)
— Provides importer functions for textures, meshes,
animations, and scene hierarchies
— Includes tight integration with MIDP
||Java Technology for the
Wireless Industry 1.0
This JSR provides an overall architectural description as well as an
integrated TCK and RI to coordinate selected JCP efforts for the
||Wireless Messaging API 2.0
— Extends JSR120 with support for Multimedia Message Service
(MMS), MIME attachments and multipart messages
— Allows for MMS content to be protected using Digital Rights
— Slimming operation of the Swing GUI toolkit from J2SE
— Java 2D graphics engine preserved
— Imaging API and Image load/save framework preserved
— Input Method framework preserved
— Pluggable Look And Feel dropped
||Content Handler API
Enabling J2ME applications to handle multi-media and web content can
give developers and users a seamless and integrated user environment on
mobile phones and wireless devices.
||Scalable 2D Vector
This specification defines an optional package API for rendering
scalable 2D vector graphics, including image files in W3C Scalable
Vector Graphics (SVG) format.
This specification defines an optional package for advanced multimedia
functionality which is targeted to run as an supplement in connection
with MMAPI (JSR-135) in J2ME/CLDC environment.
This JSR defines an API that provides culturally correct data
formatting, sorting of text strings and application resource processing
for J2ME MIDlets running in MIDP over CLDC.
||Java bindings for OpenGL ES API
This JSR provides bindings to the OpenGL ES (Embedded Subset) native 3D graphics library.
This JSR creates a mobile service architecture and platform definition for the high volume wireless handsets continuing the work started in JSR-185 and enhancing the definition with new technologies.
||Fully featured MSA
— JSR 172 Web Services
— JSR 177 Security & Trust
— JSR 179 Location
— JSR 180 SIP (for VoIP, IMS etc)
— JSR 211 Content Handler
— JSR 229 Payment
— JSR 234 Multimedia Supplements
— JSR 238 Internationalization
— JSR 248 MSA subset
||Mobile Sensor API
The API provides general Sensor API that extends the usability and
choice of sensors for J2ME applications. It defines generic sensor
functionality optimized for the resource-constrained devices like
This specification defines J2ME Optional Packages for contactless
communication, one package for bi-directional communication and the
other for accessing read-only information. As currently proposed, JSR
257 would set the stage for both one-way and bi-directional data
capture and data integration from RFID, barcode and other existing and
||Mobile Information Device Profile 3.
This JSR will specify the 3rd generation Mobile Information Device Profile, expanding upon the functionality in all areas as well as improving interoperability across devices.
||Mobile Broadcast Service API for Handheld Terminals.
This specification will define an optional package in J2ME/MIDP/CLDC environment to provide functionality to handle broadcast content, e.g. to view digital television and to utilize its rich features and services.
JSR 280 provides subsets of several key XML APIs for the Java ME platform:
— Java API for XML Processing (JAXP)
— Simple API for XML (SAX)
— Streaming API for XML (StAX, defined in JSR 173)
— Document Object Model (DOM) Core and Events
This specification will define an optional package for developing JavaTM ME applications which utilize or interoperate with DRM agents that separately exist in devices.
Project Capuchin is a Java API defining a bridge between Java ME and Adobe Flash Lite technologies.
This API makes it possible to use Flash Lite as the front end and Java ME as the back end of applications.
Project Capuchin is the base for great looking applications where the UI presentation is designed in Flash
Lite while the data logic is provided by Java code. Data transmission is enabled both ways, from Java ME
to Flash Lite and from Flash Lite to Java ME.
Project Capuchin enables faster UI development and easier collaboration between graphical designers
and code developers. Once all interfaces between the presentation and service layers have been defined,
UI designers can develop and test the presentation layer in the Flash environment independent of the Java
development and testing of the service layer.
Project Capuchin makes all services available to Java ME also available to Flash, by extending the
ActionScript API in a structured manner.
Project Capuchin improves Flash Lite content security, distribution and installation by embedding Flash
Lite content as a resource in MIDlet suites (.jar).