source :  SUN  (Staff Engineer Srikanth Raju http://srikanthraju.com)


---------------------------

Architecture de J2ME :

                       

source: http://developers.sun.com/techtopics/mobility/getstart/

):

GCF URL Schemes et Types de Connection 

------------------------------------------



Source : Didier Donsez  http://www-adele.imag.fr/%7Edonsez/cours/j2me.pdf

-------------------------------------------

Le cycle de vie d'une MIDlet :

public class Etats extends MIDlet {

    private boolean once = false;

    Mandy() {
    }

    public void startApp() {
        if ( once == false ) {
            once = true;
            // acquire one-time resources
        }
        // acquire "other" resources
    }

    public void pauseApp() {
        // release "other" resources
    }

    public void destroyApp(boolean b)
    {

    }
}

A quel moment startApp est appellé et pourquoi pauseApp est appelé ?  voir spec ...

1. Le client envoi une requete  HTTP GET au  serveur pour une  URL donnée.
2. Le serveur retourne une reponse  HTTP  avec le fichier  JAD dansle corps du message HTTP.
3. Le client verifie la reponse  HTTP et extrait les attributs  MIDlet-Jar-File et  MIDlet-Jar-Size .
4. Le client envoi une requete HTTP GET  pour demander le fichier  JAR.
5. Le serveur envoi une reponse  HTTP avec le fichier JAR dans le corps du message.
6. Le client verifie le message et le fichier  JAR.
7. L'appareil demande a l'utilisateur de utiliser l'application et la verifier.

• Connected Limited Device Configuration (CLDC) 1.1 (JSR 139)
• Mobile Information Device Profile (MIDP) 2.0 (JSR 118)
• Java Technology for the Wireless Industry (JTWI) 1.0 (JSR 185)
• Wireless Messaging API (WMA) 2.0 (JSR 205)
• Mobile Media API (MMAPI) 1.1 (JSR 135)
• PDA Optional Packages for the J2ME Platform (JSR 75)
• Java APIs for Bluetooth (JSR 82)
• J2ME Web Services Specification (JSR 172)
• Mobile 3D Graphics API for J2ME (JSR 184)

Vous pouvez utiliser aussi CLDC 1.0 et  MIDP 1.0 avec cette version.

J2ME Wireless Toolkit 2.2 inclu les nouveautés de  Wireless Toolkit 2.1, comme la signature des MIDlet, 
gestion des certificats, over-the-air (OTA) Provisioning emulation,
push registry emulation, et plus encore.


CLDC : CLDC 1.0 et CLDC 1.1 
MIDP : MIDP 1.0 et MIDP 2.0
OP   : WMA, MMAPI , M3G , Web services ...


--------------------------------------------


Installation J2ME WTK 2.2

Tout d'abord il faut avoir le JDK 1.4.2 deja installé sur le sytème (linux ou win):

 

--------------------------------
Rappel :

Le MIME type pour le 
      JAD    text/vnd.sun.j2me.app-descriptor




Et pour le              
       JAR     application/java-archive.




OTA Over The Air Provisioning :

import java.util.Date;

import javax.microedition.lcdui.Alert;
import javax.microedition.lcdui.Display;
import javax.microedition.midlet.MIDlet;

public class DateTimeApp extends MIDlet {

  Alert timeAlert;

  public DateTimeApp() {
    timeAlert = new Alert("Alert!");
    timeAlert.setString(new Date().toString());
  }

  public void startApp() {
    Display.getDisplay(this).setCurrent(timeAlert);
  }

  public void pauseApp() {
    System.out.println("Dans pauseApp");
  }

  public void destroyApp(boolean unconditional) {
    System.out.println("Dans pauseApp");
  }
}

/*


  C:\WTK22\lib
  
  
  WIN> javac -bootclasspath  C:\WTK22\lib\cldcapi11.jar;C:\WTK22\lib\midpapi20.jar DateTimeApp.java

  WIN>C:\WTK22\bin\preverify1.1.exe -classpath C:\WTK22\lib\cldcapi11.jar;C:\WTK22\lib\midpapi20.jar DateTimeApp
  
  WIN>jar -cvfm DateTimeApp.jar Manifest.mf  *.class 

  WIN>C:\WTK22\bin\emulator.exe -Xdescriptor DateTimeApp.jad

*/

Etape 7 déployer :
Configurer tout d'abord le serveur avec les Types MIME:

text/vnd.sun.j2me.app-descriptor   jad

application/java-archive           jar

---->

MIDP  OTA  provisioning :  HTTPMIDlet.java


Signer les MIDlets suites :


HTTPS  Connection  SSL/TLS :


Push Registry :


Utilisation de CustomItem :


Game API :  





Wirless Mobile  API   (WMA)  :



Mobile Media API  (MMAPI)  :

The next release of JXME 2.0, is scheduled 
for June 14th, 2005. This release will contain the new binding of JXME 
proxy-less platform on CDC1.1 ( JSR218 ). A Beta test version of JXME 2.0 
is now available.
How to get involved :

   1. Build the beta from the CVS tag "JXME_2_0_BETA"
   2. Build/Port/Rebuild your application with JXME 2.0 Beta.
   3. Test with your application.
   4. File bugs, propose patches, provide comments at discuss@jxme.jxta.org
   5. If you want to have interactive discussion, drop in MyJxta
      chat-room with MyJxta2 application or #jxta channel on
      irc.freenode.net with your favorite IRC client

The JXME Core Team

New Features & Significant Changes
------------------------------------------------------------------------

    * Full support of the core protocols
          o TCP Transport
          o Relay Transport
          o Endpoint (including the router)
          o Resolver
          o RendezVous (ad-hoc, and infrastructure edge, including edge
            side PeerView support)
          o Discovery
          o Edge side SRDI
          o Pipe
    * Simplified Programmatic Platform Configuration
          o Singleton ConfigurationFactory provides the simplest way to
            configure a peer
    * Core Services
          o Discovery Service
          o Resolver Service
          o RendezVous Service
          o Pipe Service (Unicast, and Propagate)
    * XML-Lite Support
    * Support for all core Advertisements
    * Support for all Core ID's
    * Demo Application
          o ChatDemo - J2SE interoperable group chat demo
          o GroupDemo - J2SE interoperable group, and chat demo


Downloading and Installing
------------------------------------------------------------------------
You can download the dist zip from:

Sources : http://jxme.jxta.org/files/documents/38/207/jxme_2_0_beta.zip

Binaries : http://jxme.jxta.org/files/documents/38/208/jxme_2_0_beta_bin.zip

or alternatively directly access CVS :

http://jxme.jxta.org/servlets/ProjectSource#commandlinecvs

The instruction on how to build JXME can be found at:

http://jxme.jxta.org/buildJXME20proxyless.html

hamada@jxta.org

-- 
http://blogs.sun.com/roller/page/hamada
http://weblogs.java.net/blog/hamada

What is Inca X ME?

Inca X ME is a visual platform for creating and deploying Jini services that can be accessed by either J2ME MIDP or J2SE Jini clients.

Inca X ME (micro edition) adds the following options, which allow you to create MIDP clients for your Jini services.

• MIDlet creation wizard
• Build MIDlet
• Run in emulator
• OTA provisioning
• Generate Jini service connector code