|
Explain the lifecycle of a MIDlet.The MIDlet lifecycle is the fundamental for creation of any MIDlet. The lifecycle includes the execution states such as creation, start, pause and exiting operations and a set of valid transitions. To manage the downloading and lifecycle of MIDlets, there is software by name Application Management Software. A runtime environment is provided by the AMS. The runtime environment enforces the permissions, security and the execution states & is provided the required scheduling and system classes.
Java Application Descriptor file and Java Archive are the two components that any MIDlet suite is delivered. The JAD file describes the MDIlet suite. The description comprises of the MIDlet suite’s name, location and size of the JAR file and other configuration and profile requirements.
Explain the lifecycle of a MIDlet.1. The MIDlet life-cycle is fundamental to creating any MIDlet.
2. The life-cycle defines the execution states of a MIDlet creation, start, pause, and exit.
3. A MIDlet is either in the active state or the paused state.
4. When it is first loaded by the MIDP runtime environment, it will be in the paused state.
5. The runtime will generally call the method startApp() to signal that the MIDlet should now activate itself.
6. Whenever the application is idle, the runtime can put the MIDlet back into the paused state.
7. When it is paused, the application will not receive user interface events.
8. The runtime will call pauseApp() to indicate that it has done this.
9. When the operator is finished with the MIDlet, the runtime will destroy it.
10. Before it does this, it calls the method destroyApp() method.
11. The MIDlet must deallocate resources here as it does when it enters the paused state.
12. In the MIDP documents, `destroyed' is described as being one of the states that the MIDlet may be in.
|
