Table 5: a typical sequence of midlet execution – Siemens Java TC65 User Manual
Page 35
TC65 JAVA User's Guide
Strictly confidential / Released
s
TC65 JAVA User's Guide_V05
Page 35 of 90
26.09.2005
Table 5: A typical sequence of MIDlet execution
Application Management Software
MIDlet
The application management software creates a new instance of a
MIDlet
.
The default (no argument)
constructor for the
MIDlet
is
called; it is in the Paused state.
The application management software has decided that it is an
appropriate time for the
MIDlet
to run, so it calls the
MIDlet.startApp
method for it to enter the Active state.
The
MIDlet
acquires any
resources it needs and begins to
perform its service.
The application management software no longer needs the
application be active, so it signals it to stop performing its service
by calling the MIDlet.pauseApp method.
The MIDlet stops performing its
service and might choose to
release some resources it
currently holds.
The application management software has determined that the
MIDlet
is no longer needed, or perhaps needs to make room for a
higher priority application in memory, so it signals the
MIDlet
that
it is a candidate to be destroyed by calling the
MIDlet.destroyApp
method.
If it has been designed to do so,
the
MIDlet
saves state or user
preferences and performs clean
up.