New Article: Managing the MIDlet Life-Cycle with a Finite State Machine

by

A MIDlet class may manage its own logic and life-cycle, but often a better choice is for it to delegate these responsibilities to a finite state machine (FSM). An FSM provides a simple and effective means to control your MIDlet's life-cycle and overall application behavior. This article shows you how.

Read more at: Managing the MIDlet Life-Cycle with a Finite State Machine

ceo
—
C. Enrique Ortiz
J2MEDeveloper.com
Web Page: http://www.j2medeveloper.com
Web Log: http://www.j2medeveloper.com/blog

1 thought on “New Article: Managing the MIDlet Life-Cycle with a Finite State Machine”

  1. Hi, glad to know you, here is a problem, hope to get your response. Thanks .
    I can run the program in the WTK IDE using “Run” button. After that, I use “project—>package—->create package” to create a jar and jad file for my project. Then I goto the bin diretory and open the jad file, emulator opened it successfully and the phone window showed. Nevertheless, when I click the “launch” command to launch the app, it prompted me “AppName, AppName
    Exception:java.lang.NullPointerException”.
    It seems the emulator didn’t find the app’s midp class which is the entry point and derives from Midlet. It’s very strange, because when I used “jar -xf AppName.jar” to extract the jar file, the AppName.class is right there. What’s wrong? Is there any limitation for the classes in the .jar file?
    In addition, I didn’t touch the .jad/.jar file which were created by WTK.
    Appreciate your response.
    regards
    Black hawk

Leave a Comment