Java Reference
In-Depth Information
On the Nokia N95, untrusted MIDlet suites can use the Push Registry
APIs (Application Auto-Start function group) with user permission. The
default User permission is set to Session ('Ask first time'). It can be
changed to 'Not allowed' or 'Ask every time'.
2.8 MIDP and the JTWI
The Java Technology for theWireless Industry (JTWI) initiative is part of the
Java Community Process (JSR-185) and its expert group has as its goal the
task of defining an industry-standard Java platform for mobile phones, by
reducing the need for proprietary APIs and providing a clear specification
that phone manufacturers, network operators and developers can target.
The JTWI specification concerns three main areas:
•
It provides a minimum set of APIs (JSRs) that a compliant device
should support.
•
It defines which optional features within these component JSRs must
be implemented on a JTWI-compliant device.
•
It provides clarification of component JSR specifications, where appro-
priate.
2.8.1 Component JSRs of the JTWI
The JTWI defines three categories of JSR that fall under the specification:
mandatory, conditionally required and minimum configuration. The fol-
lowing mandatory JSRs must be implemented as part of a Java platform
that is compliant with JTWI:
•
MIDP (JSR-118)
•
Wireless Messaging API (JSR-120).
The Mobile Media API (JSR-135) is conditionally required in the JTWI.
It must be present if the device exposes multimedia APIs (e.g., audio
or video playback or recording) to Java applications. The minimum
configuration required for JTWI compliance is CLDC 1.0 (JSR-30). Since
CLDC 1.1 is a superset of CLDC 1.0 it may be used instead, in which case
it supersedes the requirement for CLDC 1.0. Today most of the Symbian
OS devices in the market support CLDC 1.1.
2.8.2 JTWI Specification Requirements
As mentioned earlier, the JTWI specification makes additional require-
ments on the implementation of the component JSRs. For full details,
