This document provides an overview of EclipseME, an Eclipse plugin for developing Java ME applications. It describes how to create a new MIDlet project in EclipseME, convert an existing project, add JAR files, and upload the application to a phone. The document also includes a section on the EclipseME JAD file format which specifies metadata for the MIDlet suite.
24. Item Contents
Midlet Jar The URL from which the JAR file can be loaded.
URL
Midlet Name The name of the MIDlet suite that identifies the MIDlets to the user. Individual
MIDlets can also have names. See the Midlets tab below for that information.
Midlet The organization that provides the MIDlet suite.
Vendor
Midlet The version number of the MIDlet suite. The format is
Version <major>.<minor>.<micro> as described in the Java Product Versioning
Specification. the J2ME container can use this for install and upgrade
purposes, as well as for communication with the user.
Microedition The J2ME Configuration required by this MIDlet suite, using the same format
Configuration and value as the system property microedition.configuration. For CLDC 1.0
compatibility, this field must be CLDC-1.0. In the future, this field will be used
to specify the required CLDC version.
Microedition The J2ME profile required by this MIDlet suite, using the same format and
Profile value as the system property microedition.profiles. For the MIDP 1.0 release
the content of this field must be MIDP-1.0. In the future, this field will be used
to specify the required MIDP version.
25.
26.
27. Item Contents
Name Name of the MIDlet. If there are multiple MIDlets in your suite, when
the user invokes the suite, the J2ME device will
typically prompt the user for the specific MIDlet to be executed. This
entry provides the name that will be shown to the
user.
Icon Path to the PNG file within the JAR file that contains the icon for this
MIDlet.
Class The MIDlet class itself. This is the class you created derived from
javax.microedition.midlet.MIDlet.
28.
29. Item Contents
Midlet Permissions Permissions that your MIDlet must have in order to
operate correctly. Permissions are usually only
provided for signed MIDlets.
Optional Midlet Permissions Permissions that your MIDlet would like, but can
work without.
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.
Midlet Description The description of the MIDlet suite.
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 Manager to identify the suite. This
icon is for the suite as a whole, as distinct from the
Individual MIDlet icons you can set up on the
Midlets Tab.
Midlet Information URL A URL for information further describing the MIDlet
suite.
30.
31. Item Contents
Midlet Delete A text message provided to the user when prompted to
Confirm confirm deletion of the MIDlet suite.
Midlet Delete The URL to which a POST request is sent to confirm
Notify successful deletion of this MIDlet suite.
Midlet Install The URL to which a POST request is sent to confirm
Notify successful installation of this MIDlet suite.
32.
33. Item Contents
Key The key string used to retrieve the value.
Value The value associated with the key.
52. • In this tutorial, we are using Sony Ericsson
K700i to be an application container.
53.
54.
55.
56.
57.
58. Reference
• Core J2ME Technology and MIDP. John
W. Muchow. Prentice Hall PTR, 2002.
• Enterprise J2ME: Developing Mobile
Java Applications. Michael Juntao Yuan.
Prentice Hall PTR, 2003.
• J2ME in A Nutshell. Kim Topley. Oreilly,
2002.
• EclipseME Help.