Java Platform Micro Edition Software Development Kit
Table of Contents
- 1. Overview
- 2. System Requirements
- 3. Installation Instructions
- 4. Known Issues
- 5. Frequently Asked Questions
The Java ME Platform SDK is the first development toolbox to combine support for the following Java mobile platforms:
- CLDC 1.1 with MIDP 2.1: Get all the great features in the Sun Java Wireless Toolkit 2.5.2_01 and more, such as increased support for LWUIT, and support for JSRs 256 and 280.
- CDC 1.1 with PBP 1.1 and FP 1.1: Take advantage of advanced mobile handset features with the CDC platform.
- JavaFX 1.1 runtime: Take the mobile distribution files (JAD and JAR files) from a JavaFX application created on NetBeans and run them in the SDK to take advantage of debugging, profiling, and other mobile features.
- Blu-ray Disc Java: Create a CDC application and compile it with the BD-J stubs binary included in the SDK. The application can then be run on commercial software that supports Blu-ray playback, or saved to media and played on a Blu-ray device (such as a DVD player).
1.1 Features in this Release
Java ME SDK 3.0 Release is a software development kit (SDK). Several components comprise the Java ME SDK:
- The development environment leverages the successful NetBeans platform, providing a flexible windowing system, a logging facility, plugin modules, and autoupdate capabilities. Projects can be shared between the NetBeans Mobility Pack and the Java ME SDK.
- The emulator uses exactly the same Java ME stack that runs on real devices. The emulator is now a standalone process.
- The device manager utility manages emulators and devices. It detects emulators and devices, making them available to the SDK.
- The Unified Emulator Interface (UEI) proxy component enables IDE integration. The SDK is fully integrated with the NetBeans IDE.
To install all the components in the SDK environment, see the Installation Guide.
This release has full integration with the Netbeans 6.5 IDE. You can develop an application in NetBeans and open the project in the SDK for on-device debugging and profiling. You can test using the SDK's emulator and the Windows Mobile emulator, and even connect a real device (running Windows Mobile) to your computer for on-device debugging with the Java ME SDK.
1.2 API Support
This release implements a set of standard APIs defined through the Java Community ProcessTM (JCPTM) program:
- Mobile Information Device Profile (MIDP) 2.1 (JSR 118) *
- Connected Limited Device Configuration (CLDC) 1.1 (JSR 139)
- Connected Device Configuration 1.1 (JSR 218) *
- Personal Basis Profile 1.1 (JSR 217) *
- Foundation Profile 1.1 (JSR 219) *
- Advanced Graphics and User Interface Optional Package for the Java Platform 1.0 (JSR 209) *
- Java Technology for the Wireless Industry 1.0 (JSR 185)
- Mobile Service Architecture 1.0 (JSR 248)
- PDA Optional Packages for the J2ME Platform (JSR 75)
- Java APIs for Bluetooth (JSR 82)
- Mobile Media API (MMAPI) 1.2 (JSR 135) *
- J2ME Web Services Specification (JSR 172) *
- Security and Trust Services API for J2ME (JSR 177) *
- Location API for J2ME (JSR 179)
- SIP API for J2ME (JSR 180)
- Mobile 3D Graphics API for J2ME (JSR 184)
- Wireless Messaging API (WMA) 2.0 (JSR 205)
- Content Handler API (JSR 211) *
- Scalable 2D Vector Graphics API for J2ME (JSR 226)
- Payment API (JSR 229)
- Advanced Multimedia Supplements (JSR 234)
- Mobile Internationalization API (JSR 238) *
- Java Binding for OpenGL® ES (JSR 239)
- Mobile Sensor API (JSR 256)
- XML API for Java ME (JSR 280)
Javadoc documents for the JSRs followed by * are available in installdir
/docs/api. You can access the rest at www.jcp.org.
2. System Requirements
This section lists minimum hardware and software requirements for installation on your PC. BD-J software requirements and the device environment requirements can be addressed as necessary after the installation.
- 330 MB hard disk space
- 1 GB system RAM
- 1 GHz Pentium CPURequired SoftwareBD-J Software - only required for BD-J development
Device Environment - only required for on-device test and debug
- ActiveSync 4.5 for Windows
- Windows Mobile 6.0 platform installed on a target device with network connectivity, 32-bit RISC based microprocessor, and minimum 64 MB RAM.
- Microsoft Device Emulator
3. Installation Instructions
Follow these instructions to install the Java ME SDK.
- Verify that your system meets the preceding system requirements.
- Download Java ME Platform SDK 3.0.
- Double-click the executable file to start the installation, and follow the prompts.
- As the installation concludes, the Device Manager appears in the Windows system tray.
- To install CLDC emulation on a Windows Mobile Device or a Windows Mobile Emulator, see Java ME Platform SDK and Windows Mobile Integration [HTML] [PDF]
- To configure the BD-J environment, see "BD-J Support" in the online help.
4. Known Issues
4.1 Limitations in This Release
- The Java ME SDK runs on Window XP and Windows Vista (32-bit). Windows Vista for X64 systems will be supported in a future release.
- The Java ME SDK Emulator platform must be Windows Mobile 6 Professional. While support for other Windows Mobile platforms is possible, this release focuses on the keyboard and stylus capabilities provided by Windows Mobile 6 Professional.
- This release has been tested on both a device emulator and a single test device, but not the entire set of devices supported by Windows Mobile 6 Professional.
- The Java ME SDK supports different accounts on the same host accessing the Java ME SDK installation. This is called the Multiple User Environment. This feature is sometimes mistaken for simultaneous access by multiple users, which is not supported.
- Sometimes pressing the Help button or F1 does not display the correct help topic. You might see this behavior on wizard pages or tabs in the user interface. This happens because the window or panel you are looking at does not have focus. Click into the panel or page before clicking the Help button or F1.
4.2 Known Problems
This is not an exhaustive list of known problems. It summarizes bugs that developers are most likely to encounter while using the toolkit.
ID Description 6780780 CDC applications can't be signed. See: http://www.netbeans.org/issues/show_bug.cgi?id=155220 6750474 NetBeans doesn't detect the SDK CDC platform emulator. See http://www.netbeans.org/issues/show_bug.cgi?id=158359. 6737145 When you import a CDC project it looks for a legacy platform name that does not exist. To work around this problem, see the help topic "Create a Platform for Legacy CDC Projects". See http://www.netbeans.org/issues/show_bug.cgi?id=147370. 6748897 No way to set security domain for CDC projects. 6751506 Application Descriptor values are not saved in CDC projects. See http://www.netbeans.org/issues/show_bug.cgi?id=149916. 6752576 CDC project Build option Creating Jar panel displays an unnecessary field for JAD file name. 6775665 MMAPI-TCK:
api/javaxmicoredition/media/Player/index.html#SetMediaTimereturns incorrect media time. The emulator does not properly set the media time for MP3 media files in the REALIZED state, so LIME_MMAPI_PACKAGE > LIME_MMAPI_CLASS > getTime always returns 0.
api/java_awt/Graphics2D/index.html#GetComposite test fail in a distributed configuration
6750924 Changing the platform while creating a new project might result in a project that won't compile. For example, if you change the platform from MIDP to CDC then back to MIDP, resulting in a MIDP project with CDC library references (references are not saved). So if you revert to the first platform you must also reselect the device you chose for that platform. Note, the project doesn't always fail because some devices can support both MIDP and CDC. 6768918 CDC-TCK_112a: Three tests fail in a distributed configuration, returning java.lang.ClassNotFoundException (Class_Action and Class_Test). The tests are:
These tests pass if they are run on a single local host using AgentMain (instead of CDCAgentMain).
6799012 If a host has Windows Fast User Switching enabled, users can switch to a different account without logging off. In this environment you must exit the Device Manager before switching. If you do not, the emulator can attach to a Device Manager session you cannot see or control. 6808681 Application Descriptor custom attributes "disappear" from the project properties window, making you think the attribut was not defined. Although the values can't be seen, they are included in the Manifest file, as they should be. See http://www.netbeans.org/issues/show_bug.cgi?id=158996 6821952 The proxy for the CDC emulator cannot be set in the user interface. It can be set from the command line as follows:
6825321 If the SDK is running and you exit the device manager certain tools such as the WMA console and the Network Monitor do not work properly. If you exit the device manager you should restart the SDK. 6823628 Pressing F1 for help in the device properties window results in a null pointer exception. See http://www.netbeans.org/issues/show_bug.cgi?id=161652.
5. Frequently Asked Questions
For answers to common questions, see the FAQ.
To comment on this release, please submit your feedback at:
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.