Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Revision as of 06:02, 24 July 2013 by hamishwillee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

MIDlet JAR Manifest essentials

From Wiki
Jump to: navigation, search

Needs-update.pngThis article needs to be updated: If you found this article useful, please fix the problems below then delete the {{ArticleNeedsUpdate}} template from the article to remove this warning.

Reasons: hamishwillee (27 Mar 2013)
This article should be merged with articles containing similar material: JAD, JAR, Java Application Descriptor (JAD) essentials, MIDlet JAR Manifest essentials



The manifest provides information about the contents of the JAR file. MIDP implementations MUST implement handling of lines longer than 72 bytes as defined in the manifest specification. An attribute MUST not appear more than once within the manifest. If an attribute is duplicated the effect is unspecified. Manifest attributes are passed to the MIDlet when requested using the MIDlet.getAppProperty method, unless the attribute is duplicated in the application descriptor

Article Metadata
Created: adilb (25 May 2007)
Last edited: hamishwillee (24 Jul 2013)

Warning.pngWarning: MIDlet attributes must be the same in both JAR manifest and the JAD! Otherwise the application will not work after being signed.
For more information on signing and Java verfied see this FAQ. In particular topics "Signing Java ME applications" and "Why doesn't my signed midlet work?"

Must Have Attributes

  • MIDlet-Name :The name of the MIDlet suite
  • MIDlet-Version :The version number of the MIDlet suite.
  • MIDlet-Vendor :The name of vendor that provides/creates the MIDlet suite.
  • MIDlet-<n> for each MIDlet :The name, icon, and class of the nth MIDlet in the JAR file separated by a comma. The lowest value of <n> MUST be 1 and consecutive ordinals MUST be used. The first missing entry terminates the list. Any additional entries are ignored. Leading and trailing spaces in name, icon and class are ignored.
  • MicroEdition-Profile :The MIDprofile veing used eg:MIDP1.0
  • MicroEdition-Configuration :The Configuration being used eg:CLDC1.0

May contain Attributes

  • MIDlet-Description :Usually a short discription about the MIDlet
  • MIDlet-Icon :Its the absolute name of a PNG file within the JAR used to represent the MIDlet suite. It is the icon that the AMS(Application Management Software) displays.
  • MIDlet-Info-URL :A URL for information describing the MIDlet suite.
  • MIDlet-Data-Size :The data storage size that can be used eg:1024
  • MIDlet-Permissions :Zero or more permissions that are critical to the function of the MIDlet suite.
  • MIDlet-Permissions-Opt :Zero or more permissions that are non-critical to the function of the MIDlet suite.
  • MIDlet-Push-<n> :Register a MIDlet to handle inbound connections.
  • MIDlet-Install-Notify : The URL to be notified after installation of MIDlet
  • MIDlet-Delete-Notify : The URL to be notified after deletion of MIDlet
  • MIDlet-Delete-Confirm

Any application-specific attributes that do not begin with MIDlet- or MicroEdition- which can be read later in code

See also

This page was last modified on 24 July 2013, at 06:02.
58 page views in the last 30 days.