TABLE 6 – MIDlet Attributes
|
Attribute Name
|
Attribute Description
|
Attribute File
|
|
Required Attributes
|
|
|
|
MIDlet-Name
|
The name of the MIDlet suite that identifies the MIDlets to the user.
|
JAD and manifest
|
|
MIDlet-Version
|
The version number of the MIDlet suite. The format is <major>.<minor>.<micro> as described in the Java Product Versioning Specification. It can be used by the application management software for install and upgrade purposes, as well as for communication with the user.
|
JAD and manifest
|
|
MIDlet-Vendor
|
The organization that provides the MIDlet suite.
|
JAD and manifest
|
|
MIDlet-Jar-URL
|
The URL from which the JAR file can be loaded.
|
JAD
|
|
MIDlet-Jar-Size
|
The number of bytes in the JAR file. A development environment should automatically generate this field when the JAR file is built (and prevent it from being edited by the user).
|
JAD
|
|
MicroEdition-Profile
|
The J2ME profile required, using the same format and value as the system property microedition.profiles. For the MIDP 2.0 release, the content of this field must be MIDP-2.0.
|
manifest
|
|
MicroEdition-Configuration
|
The J2ME Configuration required using the same format and value as the system property microedition.configuration.
|
manifest
|
|
Optional Attributes
|
|
|
|
MIDlet-Icon
|
The name of a PNG file within the JAR file used to represent the MIDlet suite. It is the icon used by the Java Application Management System to identify the suite.
|
JAD and/or manifest
|
|
MIDlet-Description
|
The description of the MIDlet suite.
|
JAD and/or manifest
|
|
MIDlet-Info-URL
|
A URL for information further describing the MIDlet suite.
|
JAD and/or manifest
|
|
MIDlet-Data-Size
|
The minimum number of bytes of persistent data required by the MIDlet. The device may provide additional storage according to its own policy. The default is zero.
|
JAD and/or manifest
|
|
MIDlet-Delete-Confirm
|
A text message provided to the user when prompted to confirm deletion of the MIDlet suite.
|
|
|
MIDlet-Delete-Notify
|
The URL to which a POST request is sent to report deletion of the MIDlet suite.
|
|
|
MIDlet-Install-Notify
|
The URL to which a POST request is sent to confirm successful installation of this MIDlet suite.
|
|
|
<User-Defined Attributes>
|
User-defined attributes relating to specific MIDlets. See Table X for a list of user-defined attributes for MMAPI MIDlets
|
JAD
|
|
MIDlet-n Attributes
|
|
|
|
MIDlet-<n>
|
The name, icon, and class of the nth MIDlet in the JAR file. The lowest value of <n> must be 1 and consecutive ordinals must be used.
The MIDlet’s name identifies it to the user.
The MIDlet’s icon is specified by the name of a PNG image within the JAR.
The MIDlet’s class is specified by the name of a class that extends MIDlet and has a public no-argument constructor.
|
manifest
|
|
MIDlet-Push-<n>
|
The connection URL, class, and allowed sender of the nth MIDlet in the JAR file. The lowest value of <n> must be 1 and consecutive ordinals must be used.
The MIDlet’s connection URL identifies the connection protocol and port number.
The MIDlet’s class name. If the given MIDlet appears multiple times in the suite, the first matching entry is used.
The allowed sender is a valid sender that can launch the associated MIDlet.
|
JAD
|
|
MIDlet-Permissions
|
Permissions for required APIs, which are APIs that the MIDlet suite must have access to in order to function.
Permissions have the same naming structure as a Java class, for example, javax.microedition.io.Connector.http
|
JAD and manifest
|
|
MIDlet-Permissions-Opt
|
Permissions for non-required APIs, which are APIs that are not essential for the MIDlet suite to function. The MIDlet suite is able to run with reduced functionality.
Permissions have the same naming structure as a Java class, for example, javax.microedition.io.Connector.http
|
JAD and manifest
|
|
