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 over the next few weeks. Thanks for all your past and future contributions.

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

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


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

Article Metadata
Created: firt (09 Apr 2007)
Last edited: hamishwillee (24 Jul 2013)

Java Application Descriptor (JAD) is a text file that describes a MIDlet or a suite of them, distributed as a JAR file. The file has a .jad extension and the name is selected by the developer.

This file is useful for the operating system of the mobile phone to detect requirements, names, icons of the application or game to be installed, before download or installing it.

The syntax of the file is:

Key: Value
Key2: Value2

There are a number of mandatory attributes, which need to be in the JAD file (or then in the Manifest file inside the JAR file), but you can also insert your own attributes in the JAD file, to convey information for your MIDlet (like server to connect to, etc.). The only restriction for those attributes is that the keys (attribute names) cannot start with "MIDlet" or "MicroEdition".

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?"

Mandatory Information

  • MIDlet-1: defines the class name of the main MIDlet in the JAR.
  • MIDlet-Jar-Size: defines the size (in bytes) of the JAR file to install.
  • MIDlet-Jar-URL: defines the name and URL of the JAR file. It can be just the name of the JAR if it's located in the same place, or a full URL (like
  • MIDlet-Name: defines the name of the suite that appears on the phone main menu
  • MIDlet-Vendor: defines the company who develops the application
  • MIDlet-Version: defines the version number of the application
  • MicroEdition-Configuration: defines the configuration, like CLDC-1.1
  • MicroEdition-Profile: defines the profile used, like MIDP-2.0

Additional Information

*MIDlet-Certificate: If the application is signed, the details are provided
*MIDlet-Jar-RSA : If the application is signed, the details are provided
*MIDlet-LOG-PATH : This is a user defined sample entry, just to provide the filesystem path, so that you don't need to hardcode it anywhere in the source


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

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.