Release NotesSun Java Wireless Client Software 2.2December 2008 |
Sun Java Wireless Client Software (SJWC) is an optimized Java Platform, Micro Edition (Java ME) stack. This implementation supports multitasking and is built upon MIDP 2.1. For more information about Sun Java Wireless Client Software, see Software Overview.
The following features are part of Sun Java Wireless Client Software, version 2.2:
NOTE: This release is not fully MSA-compliant, as the 3D Graphics optional package (JSR 184) is not included in this distribution.
Following are the supported target platforms for running an implementation of Sun Java Wireless Client Software:
For more information on platform compatibilities, build tools, and other build considerations, see the Sun Java Wireless Client Software Build Guide.
The Win32 binary pack (found in bundle 3 of the Java License Engineering Sun Java Wireless Client software districubution), should be used as a base for running binaries that customers buid themselves. The Win32 binary pack is a complete implementation of the Mobile Information Device Profile (MIDP), without any additional Java Specification Request (JSR) optional packages.
The Sun Java Wireless Client contains an implementation of the Java ME SDK 3.0, which provides an emulation environment on the Windows platform. Although it is possible to use the Wireless Toolkit (WTK) 2.5.2 as your emulation environment, it is not recommended. WTK 2.5.2 has not been fully tested with the Sun Java Wireless Client software and many features of the Wireless Toolkit are not supported.
Do not start the VM when some BT push MIDlet is installed. If you try to start the VM with a test MIDlet installed, the emulator will crash. During TCK execution, after the accidental exit from the emulator with the installed test MIDlet, it's impossible to start the emulator again.
This happens because a notifier must be created on the Java platform level, to start a BT push emulator notifier to listen for the push connection. However, the moment the push server starts during the VM startup process, there is no Java platform thread and the system crashes.
If the emulator crashes with a test MIDlet installed, you can restart the emulator by following these steps:
appdb directory.
This problem exists for the emulator implementation only.
The following bugs are known at the time of this release.
| BUG ID | DESCRIPTION |
|---|---|
| 6737261 | ScrollArrowLayer's arrow does not always scroll when used with a pointer device. |
| 6782244 | Predict bar flashing while moving through the Menu. |
| 6782135 | Java Device Test Suite: Some MIDP tests fail. |
| 6780696 | Java Device Test Suite: Video disappears and does not reappear. |
| 6759236 | Java Device Test Suite: Some testBadFormat tests fail. |
| 6758680 | Java Device Test Suite: Some SIP_API_(JSR_180)/com/sun/sip/push tests fail. |
| 6756098 | Java Device Test Suite: ui/lowUI/graphics/arc/PositiveArcs#FilledArc |
| 6756089 | Java Device Test Suite: ui/lowUI/display/EmptyDisplay#NullCanvas |
| 6754688 | Java Device Test Suite: SVGTinyElementsTest#allSVGTinyElements test |
| 6683129 | Image cannot be scrolled backward or forward. |
| 6679019 | Java Device Test Suite: PlatformRequest tests in MIDP are failed. |
| 6678395 | Java Device Test Suite: Two midlet/MidletTests in MIDP OTA are failed. |
| 6537809 | Java Device Test Suite: All com/sun/midp2_0/functional/network tests are failed. |
Copyright © 2008 Sun Microsystems, Inc. All rights reserved. SUN PROPRIETARY/CONFIDENTIAL.