This document defines the scope of SquirrelJME, classes which are to be supported and ones which are not to be supported. All the listed specifications are either planned to be implemented, considering, or out of scope for the project.

This scope is up-to-date as of March 2026.

To Implement

These are specifications which are to be implemented to provide the base functionality for SquirrelJME.

Specifications

All of these listed specifications are not obsolete or implemented by other specifications.

• JSR184 -- Mobile 3D Graphics API for J2ME
  • Needed by a number of games.
• JSR211 -- Content Handler API
  • Content handling, essentially say you install a JAR that is a media player for MIDI files. Effectively if you "launch" a MIDI, that given JAR will open to view the given content.
• JSR226 -- Scalable 2D Vector Graphics API for J2ME 1.1
  • SVG Tiny Support.
  • Relies on LCDUI.
  • Some classes can just forward calls to MIDP 3.
• JSR238 -- Mobile Internationalization API
  • Internationalization of text.
• JSR239 -- Java Binding for the OpenGL ES API
  • Required for some games.
  • Can be more easily bridged to native OpenGL implementations compared to M3G.
• JSR256 -- Mobile Sensor API 1.2
  • Sensors are useful.
• JSR271 -- Mobile Information Device Profile 3
  • Enhances support for MIDlets by adding more features.
  • MIDP 3.0
• JSR360 -- Connected Limited Device Configuration 8
  • This is SquirrelJME's target.
• JSR361 -- Java ME Embedded Profile
  • MEEP 8.
  • This is SquirrelJME's target.

Considering

Specifications that may be considered for inclusion.

Specifications

• JSR120 -- Java(TM) Wireless Messaging API Specification 1.1
  • Supports SMS, USSD, and CBS.
  • Uses GCF.
• JSR179 -- Location API for J2ME.
  • Locating of users via GPS and other such things.
• JSR230 -- Data Sync API 0.9
  • Similar to Palm OS's HotSync.
• JSR257 -- Contactless Communication API
  • Can be used for RFID and such.
  • May also include NFC.

CDC, PBP, and AWT Requiring

These generally all include a partial or full AWT implementation and as such require a more complete ScritchUI to handle properly.

• JSR062 -- Personal Profile Specification.
  • Effectively Java SE Embedded.
• JSR129 -- Personal Basis Profile Specification
  • Effectively Java SE Embedded.
• JSR209 -- Advanced Graphics and User Interface.
  • Effectively Java SE Embedded.
• JSR216 -- Personal Profile.
  • Effectively Java SE Embedded.
• JSR217 -- Personal Basis Profile 1.1.2
  • Effectively Java SE Embedded.
• JSR218 -- Connected Device Configuration (CDC) 1.1
  • CDC.
• JSR927 -- Java TV API 1.1
  • Depends upon JSR127 (Personal Basis Profile).
  • Precedes BD-J.
  • Includes javax.tv.xlet.

Non-JSR Specifications

• Java Applets -- Standard Java Applets
  • Requires AWT
• BD-J -- Blu-ray Disc Java (Blu-ray Disc Association)
  • Extends on Java TV (includes the Personal Basis Profile).
  • Not a JSR, standardized by the specified association.

Out of Scope

These specifications will be not be implemented at all. Note however, that although these specifications are out of scope may potentially be provided by third parties libraries.

Specifications

• JSR066 -- RMI Optional Package Specification Version 1.0.
  • Requires CDC.
• JSR169 -- JDBC Optional Package for CDC/Foundation Profile
  • Requires CDC.
• JSR172 -- J2ME Web Services 1.1
  • XML is nasty.
  • Designed for both CLDC and CDC.
• JSR177 -- Security and Trust Services API for J2ME
  • Some classes are partially handled by other implemented JSRs.
• JSR180 -- SIP API for J2ME.
  • Voice calls.
  • Uses GCF.
  • This is really handled best by third party providers.
• JSR197 -- Generic Connection Framework Optional Package for J2SE.
  • Not J2ME related, however it is included to reduce confusion.
  • Makes it so Java SE can use GCF.
• JSR219 -- Foundation Profile 1.1.2
  • Effectively Java SE with Java ME bits.
• JSR229 -- Payment API
  • Used for monetary transactions.
• JSR232 -- Mobile Operational Management
  • CDC.
• JSR242 -- Digital Set Top Box Profile - "On Ramp to OCAP"
  • Effectively Java SE.
  • Has TV stuff.
• JSR272 -- Mobile Broadcast Service API for Handheld Terminals 1.0
  • This is for broadcast services, which is completely out of scope.
• JSR302 -- Safety Critical Java Technology
  • Essentially JSR001 for J2ME.
  • Real time does not always mean safe.
• JSR325 -- IMS Communication Enablers
  • Essentially VoIP.
• JSR332 -- Email Client API for Java ME
  • E-mail.

Obsolete

These specifications are obsolete and are implemented by newer specifications.

• JSR30/JSR030 -- J2ME Connected, Limited Device Configuration.
  • Implemented by newer JSR.
  • CLDC 1.0.
• JSR37/JSR037 -- Mobile Information Device Profile for the J2ME Platform.
  • Implemented by newer JSR.
  • MIDP 1.0.
  • Contains the Limited Capability Device User Interface (LCDUI).
• JSR75/JSR075 -- PDA Optional Packages for the J2ME Platform
  • Implemented by newer JSR.
  • Contains file related javax.microedition.io classes.
• JSR118 -- Mobile Information Device Profile 2.0
  • Implemented by newer JSR.
  • MIDP 2.0.
• JSR135 -- Mobile Media API
  • Implemented by newer JSR.
  • Multimedia.
  • Implemented by MIDP 3.
• JSR139 -- Connected Limited Device Configuration 1.1
  • Implemented by newer JSR.
• JSR195 -- Information Module Profile Documentation
  • Implemented by newer JSR.
  • Essentially HTTPConnection and MEEP-8's rms.
  • CLDC 1.1.
• JSR228 -- Information Module Profile - Next Generation (IMP-NG)
  • Implemented by newer JSR.
  • An early ancestor to MIDP 3 and MEEP.
• JSR234 -- Advanced Multimedia Supplements.
  • Implemented by newer JSR.
  • Included by MIDP 3.
• JSR246 -- Device Management API
  • Implemented by newer JSR.
  • Included by Java ME 8.

Withdrawn and Rejected

These are JSRs which were proposed but then withdrawn or rejected, so they never went through the process of standardization.

Specifications

• JSR068 -- J2ME Platform Specification
  • Withdrawn.
  • Based on the description it uses "building blocks" which could also be known as profiles. SquirrelJME already has such things in the project system.
• JSR178 -- Mobile Game API
  • Withdrawn.
  • Based on the description it would essentially be a game library with multiplayer APIs, collisions, vector graphics, and a physics engine.
• JSR213 -- Micro WSCI Framework for J2ME.
  • Rejected.
  • More nasty XML.
  • Requires CDC.
• JSR214 -- Micro BPSS for J2ME Devices.
  • Rejected.
• JSR324 -- On Screen MIDlet API for Java ME
  • Rejected.
  • Essentially stuff related to the idle screen, likely similar to MIDP 3.

Unknown

These are specifications which the understanding of them is not enough to evaluate them completely for inclusion or exclusion.

Specifications

• JSR190 -- Event Tracking API for J2ME
  • IPDR/SP? Internet Protocol Detail Record.
  • Not sure if this is for events that happen (say temperature changes) or if something bad happens to hardware.

Non-JSR Vendor Specific APIs

These are APIs which are vendor specific, these vendors generally have their own implementation that later has become a JSR even if no device actually implements said JSR, an example being MIDP 3.

• Danger HipTop
• JBlend
• JPhone
• LG MMPP
• Mascot Capsule 3D
• Nokia
• NTT DoCoMo DoJa
• NTT DoCoMo Star
• Samsung
• Siemens
• SKT
• SprintPCS
• WIPI
• Vodafone