For example, a manifest for a hypothetical suite of card games would look like the following example:. All Java classes needed by the MIDlet are be placed in the JAR file using the standard structure, based on mapping the fully qualified class names to directory and file names.
For example, a class com. The application descriptor is used in conjunction with the JAR manifest by the application management software to manage the MIDlet and is used by the MIDlet itself for configuration specific attributes.
The descriptor allows the application management software on the device to verify that the MIDlet is suited to the device before loading the full JAR file of the MIDlet suite.
It also allows configuration-specific attributes parameters to be supplied to the MIDlet s without modifying the JAR file. A predefined set of attributes is specified to allow the application management software to identify, retrieve, and install the MIDlet s. All attributes appearing in the descriptor file are made available to the MIDlet s. The developer may use attributes not beginning with MIDlet- or MicroEdition- for application-specific purposes. Attribute names are case-sensitive and MUST match exactly.
Duplication of other manifest attributes in the application descriptor is not required and their values MAY differ even though both the manifest and descriptor files contain the same attribute for untrusted MIDlet suites. If the MIDlet suite is not trusted the value from the descriptor file will override the value from the manifest file. Generally speaking, the format of the application descriptor is a sequence of lines consisting of an attribute name followed by a colon, the value of the attribute, and a carriage return.
White space is ignored before and after the value. The order of the attributes is arbitrary. For example, an ISO encoded file would need to be read through the equivalent of java. InputStreamReader with the appropriate encoding.
The default character encoding for transporting a descriptor is UTF For example, an application descriptor for a hypothetical suite of card games would look look like the following example:.
The MIDlet can request the arguments from the application descriptor to communicate with the application management software.
If it exists, it MUST be ignored by the application management software. When a MIDlet suite is installed on a device, its classes, resource files, arguments, and persistent storage are kept on the device and ready for use. The MIDlet s are available to the user via the device's application management software. The MIDlet can either request changes in state or notify the application management software of state changes via the MIDlet methods.
When the MIDlet is finished or terminated by the application management software, it is destroyed, and the resources it used can be reclaimed, including any objects it created and its classes. The normal states of Java classes are not affected by these classes as they are loaded. Referring to any class will cause it to be loaded, and the normal static initialization will occur. Extended by a MIDlet to allow the application management software to start, stop, and destroy it.
The MIDlet can signal the application management software about whether is it wants to run or has completed. More specific application states are known only to the application. The MIDlet state machine is designed to ensure that the behavior of an application is consistent and as close as possible to what device manufactures and users expect, specifically:.
The MIDlet is initialized and is quiescent. This state is entered:. After the MIDlet has been created using new. The public no-argument constructor for the MIDlet is called and returns without throwing an exception. The application typically does little or no initialization in this step. If an exception occurs, the application immediately enters the Destroyed state and is discarded. From the Active state after the MIDlet. From the Active state when the MIDlet. The MIDlet has released all of its resources and terminated.
The destroyApp method shall release all resources held and perform any necessary cleanup so it may be garbage collected. When the MIDlet. A single JAR file contains all the classes of the application. All of the classes, class state, static variable data and static initializers within these scopes are unique in the execution environment provided by the AMS for the application. All states accessible via those classes are available to any Java class running on behalf of the application.
When an application that depends on one or more LIBlets is launched, all the code of the application and LIBlets is executed in an execution environment, indistinguishable from a standalone application packaging all the application and LIBlet code in a single application JAR.
The act of loading an application with all the associated LIBlets it declares dependencies on directly or indirectly into a single execution environment is called binding. Once bound, the LIBlet code is executed within the application execution environment as if it were packaged into the application JAR. Thus, although a LIBlet bound to different applications may access shared persistent resources through RMS or other persistent storage, the execution of its code inside different bindings will be completely isolated from each other.
The files from the JAR that are not Java class files are made available via java. The contents of the application descriptor file, when it is present, are made available via the javax. This method cannot be used to retrieve contents of the LIBlet descriptor file. The javax. This method retrieves a property value for a specific LIBlet or application, so the same property name is allowed to be used by multiple LIBlets without ambiguity in the binding.
Auto Start Applications Applications that are auto-started by the device on power-up and restarted on exit of the application are called "Auto Start Applications". The AMS MUST attempt to start the application immediately after installation or update and on power-up; however, the system MAY fail start such applications due to resource constraints.
If the attribute value includes autostart , the application assumes the Auto Start Application behavior. The application must have the javax. AutoStartPermission for an application to assume this behavior. Version Numbering Version numbers have the format Major. Micro] X. X] , where the. Micro portion MAY be omitted. If the. Micro portion is omitted, then it defaults to zero.
In addition, each portion of the version number is allowed a maximum of two decimal digits i. Version numbers are described in [ JPVS ]. For example, 1. For each portion of the version number, leading zeros are not significant. For example, 08 is equivalent to 8. Also, 1. However, 1. Application Classes All Java classes needed by the application are be placed in the JAR using the standard structure, based on mapping the fully qualified class names to directory and file names.
For example, a class com. The application class allows for the orderly starting, stopping, and cleanup of the application. The application can request the arguments from the application descriptor to communicate with the application management software. Unlike other Java application environments, applications of MEEP 8 do not use the public static void main String[] method as their entry point.
Instead, the methods of the initial application class are called as defined by the application lifecycle model. When an application suite is installed on a device, its classes, resource files, arguments, and persistent storage are kept on the device and ready for use.
The application s are available via the device's application management software. When the application is run, an instance of the application's primary class is created using its public no-argument constructor, and the methods of the application are called to sequence the application through its various states.
The application can either request changes in state or notify the application management software of state changes via the application methods. When the application is finished or terminated by the application management software, it is destroyed, and the resources it used can be reclaimed, including any objects it created and its classes.
The normal states of Java classes are not affected by these classes as they are loaded. Referring to any class will cause it to be loaded, and the normal static initialization will occur. The application lifecycle defines the protocol between an application and its environment through the following: A simple well-defined state machine A concise definition of the application's states APIs to signal changes between the states Application Lifecycle Definitions The following definitions are used in the application lifecycle: application management software - a part of the device's software operating environment that manages applications.
It maintains the application's state and directs the application through state changes. Application - an instance of javax. MIDlet on the device. Description Keep your SMS messages secret. Free 14 day trial. Write a message. Set the code. Send a message. Receive a message.
Decode the message. Coded messages look like this: Wpdmlyet! Features: Write messages. Receive messages. Set the message Play the best game in the world, while developing your mind.
Mental transformations increase your IQ. Play standard, play upside-down futrix, play towers. Description Play the best game in the world, while developing your mind.
Features: Resizes everything to fit on your screen. Fly through mountains and cave systems eliminating multiple enemies before finally destroying the Pirate Base.
Freeware - Download Now. Pick up weapons, shield and fuel power ups along the way. Multiple levels, terrains and enemies. Since the creation of trade routes between Earth and Mars AD the Aranaxus crime Syndicate have been pirating the cargo vessels. Recent intelligence has uncovered what appears to be a
0コメント