Release Notes

Sun Java™ Wireless Client Software 2.1

April 2008

 

Table of Contents

Introduction
Platform Requirements
Implementation Notes
Known Bugs

Introduction

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.1:

Platform Requirements

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.

Implementation Notes

MT-QTS No Longer Supported

Support for the Multitasking Quality Test Suite (MT-QTS) has been dropped in Sun Java Wireless Client Software 2.1. Future support for Multitasking Test Suite will be made available in the next release of the Java Device Test Suite (JDTS), which is currently in Beta.

Quick Key Presses in WTK 2.5.2 Can Lose Key Strokes

The Sun Java Wireless Client software is dependent on components of WTK 2.5.2 for emulation on Win32 platforms. In SJWC software builds on Win32 platforms with Wireless Toolkit 2.5.2, very quick, repeated keypresses from QWERTY keyboards can be lost. To bypass the problem, press repeated keys with a pause of 500ms or more. Users should be careful typing passwords and URLs. (See bug 6682099 in Known Bugs, below.)

JAVA_HEAP_SIZE Property Value Incorrect

MIDlets installed in SVM mode are unable to be run twice, with no error messages appearing in the console. The problem is caused by an incorrect value in JAVA_HEAP_SIZE in the jwc_properties.ini file. (See bug 6680850 in Known Bugs, below.)

Source Root Directory Path Length May Cause Unpredictable Build Crashes

Due to an inconsistency in Cyg4me, SJWC source root directory path names that are too long or too short may (or may not) cause make to crash during building, with the following error message:

There are no strict rules for how long or how short a source root directory path must be to successfully sidestep this bug. If it occurs, work around it by shortening or lengthening your source root directory path names. (See bug 6393610 in Known Bugs, below.)

Known Bugs

The following bugs are known at the time of this release.

BUG ID DESCRIPTION

6393610 MIDP build crashes with following message: STATUS_ACCESS_VIOLATION. Workaround: shorten or lengthen root directory path names in build makefiles.
6674059 Problem of communication between test MIDlet and partnerMIDlet.
6675509 Fonts at different styles and weights are the same, as there is only one font weight and style in the Scalable Vector Graphics (SVG) engine.
6675571 Event is not delivered to dedicated shape if size of the shape is dynamic: either size is not recalculated after incrementTime (size recalculation is delayed) or event processing routing uses cached value of the size.
6676172 Text that should be red and green is black.
6678408 Red and green icons of installed MIDlets are not the same.
6679076 Problem of communication between test MIDlet and partnerMIDlet.
6680437 Error in tone sequence correctness check procedure.
6680850 Configuration problem: jwc_properties.ini contains JAVA_HEAP_SIZE= 4194304 (instead of 1280*1024) even when building SVM. Workaround: put the correct value of the JAVA_HEAP_SIZE property into jwc_properties.ini.
6682099 Specific JavaCall API for WTK implementation issue - to be solved during porting to particular platform. Key-typed WTK events generated JAVACALL_KEYPRESSED events only, no paired JAVACALL_RELEASED were posted to MIDP. It caused noticeable delay for multiple character typing from keyboard. The problem appears only if some key is pressed quickly more than one time (like 'ss' in the word 'password'); it's possible to pass test pressing keys with some delay.