JSR 118 Maintenance release change log


Maintenance lead : Paul Su, Aplix Corportion.
Email id : paulsu@aplixcorp.com

Maintenance release version : From 2.1 to 2.2

Number Changes Reason Status
1
Include support for parsing and handling IPv6 addresses

With MIDP 2.x being increasingly targeted toward feature phones in emerging markets and the number of those devices increasing, the range of IP addresses available from IPv4 will be too limited to support expected future shipments. Support for parsing of IPv6 addresses will address this concern.
2 Remove section on Blanket settings for Auto Invocation and Net Access.                                                                                                                                                                                                               The JSR 118 MIDP 2.1 Specification states :
the Blanket setting for Application Auto Invocation and the Blanket setting for Net Access are mutually exclusive.

However, the JSR 248 MSA Specification states:
the Blanket setting for Application Auto Invocation and the Blanket setting for any of:
 - Net Access
 - Low Level Net Access
are mutually exclusive

This requirement was removed in the changes between the MSA and MSA 2 specifications. It should be removed from the MIDP 2 specification to maintain consistency.

3 Update references to MIDP 2.0
Update specification version number from 2.0 to 2.2 as necessary.

4 Update references to J2ME
Update J2ME references to Java ME as necessary.
5 Add missing acronym definitions in the Definitions section
From Chapter 2
"The terminology used herein is defined in the Definitions section of the MIDP 2.0 specification except where noted."

Acronyms and terms used throughout the MIDP 2 specification are not covered in the Definitions table as stated.
6 Remove statement "Untrusted MIDlet suites do not request permissions explicitly in the JAR manifest or application descriptor." This statement conflicts with the MIDP 3.0 requirement that all MIDlets explicitly define the permissions they require. Removing the statement introduces some ambiguity but resolves the direct conflict allowing for easier migration to MIDP 3.0.
7 Fix font formatting in Section 15.3
The 3rd paragraph in Section 15.3 has larger-than-normal text.
8 Fix punctuation in section 15.3 ”another Certificate” should have a period after it.

“Applications signed with a certificate not bound to any protection domains, MUST NOT be installed on the device.”
9 Fix typo in section 15.4.1

“pplication” is misspelled.
10
Fix formatting in section 15.6

The first 3 sentences in Section 15.6 need to be combined into one paragraph.

Section 15.6, “Presenting Function Group Information” should be formatted as a heading.
11 Apply MSA 2 clarification:

For a MIDlet in the foreground, calling any of the Display.setCurrent() methods SHOULD reset any current timers for power saving measures to keep the visibility from immediately disappearing. This has the same effect as user input like a key or touch screen press with the keylock off. Where applicable this includes system operations such as turning/keeping backlight on, as well as resetting the timeouts for home screen, screen saver, etc.

MSA 2 FD v0.54 Section 6.16.3.16
12 Apply MSA 2 clarification:

Certificates available in public certificate stores of the default preinstalled browser for use with HTTPS connections MUST also be available for HTTPS connections from MIDlets. Certificates in non-public certificate stores MAY not be available for MIDlets. Note that this requirement only applies if the related application (web browser) is present on the device. The requirement MAY also have limited support on emulators in development environments.

MSA 2 FD v0.54 Section 6.16.3.17
13 Apply MSA 2 clarification:

Implementations MUST ensure that the Discovery Agent(s) prebuilt into the device include the product tokens for device manufacturer, device model identifier and device software version in the HTTP User-Agent request header.
MSA 2 FD v0.54 Section 6.16.3.18
14 Remove requirement for mandatory support of Canvas repeat events The repeat event requirement was introduced without consideration for keyless, touch screen-only devices which are unable to generate repeat events