Methods Summary |
---|
public void | initCleanupMonitor(com.sun.midp.main.MIDletProxyList midletProxyList)Setup to monitor for MIDlets starting and exiting and check
for incompletely handled Invocation requests.
Cleanup only occurs within the AMS Isolate.
This method is only called from MIDletSuiteLoader in the AMS Isolate.
midletProxyList.addListener(this);
|
public void | midletAdded(com.sun.midp.main.MIDletProxy midlet)The ContentHandler monitor ignores MIDlet added callbacks.
The necessary initialization is done in the Isolate and
MIDletState that instantiates the MIDlet.
Called when a MIDlet is added to the list and only in the AMS
Isolate.
|
public void | midletInit(int suiteId, java.lang.String classname)Notification that a MIDlet is about to be created.
Set the cleanup flag on all invocations for the MIDlet.
InvocationStore.setCleanup(suiteId, classname, true);
|
public void | midletRemoved(com.sun.midp.main.MIDletProxy midlet)The ContentHandler monitor uses the MIDlet removed callback
to cleanup any Invocations in an incorrect state.
Called (in the AMS Isolate) when a MIDlet is removed from the list.
AppProxy.getCurrent().logInfo("midletRemoved: " +
midlet.getClassName());
// Cleanup unprocessed Invocations
RegistryImpl.cleanup(midlet.getSuiteId(), midlet.getClassName());
// Check for and execute a pending MIDlet suite
InvocationImpl.invokeNext();
|
public void | midletStartError(int externalAppId, int suiteId, java.lang.String className, int errorCode, java.lang.String errorDetails)Called when error occurred while starting a MIDlet object.
|
public void | midletUpdated(com.sun.midp.main.MIDletProxy midlet, int fieldId)The ContentHandler monitor ignores MIDlet update callbacks.
Called when the state of a MIDlet in the list is updated.
|