1 / 78

Agenda

1. Agenda. History Java Universe Understanding Java ME Configuration Profile Java ME : CLDC Java ME : MIDP. 2. History. 1990: Java started as an internal project at Sun Microsystems 1995: Initial release of JDK 1.0 (applets  servlets) 1999: JavaOne conference

cianna
Télécharger la présentation

Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 1

  2. Agenda • History • Java Universe • Understanding Java ME • Configuration • Profile • Java ME : CLDC • Java ME : MIDP 2

  3. History • 1990: Java started as an internal project at Sun Microsystems • 1995: Initial release of JDK 1.0 (applets servlets) • 1999: JavaOne conference • Subdivision of Java in • Java 2 Enterprise Edition (J2EE) • Java 2 Standard Edition (J2SE) • Java 2 Micro Edition (Java ME) (successor of Personal Java and • Embedded Java) • 2000/01 First mobile phones with support for J2ME 3

  4. Java Universe 4

  5. What is Java ME? • Java ME : Java 2 Platform, Micro Edition • “Java for small devices” • Java ME is downsized version on • J2SE • It is currently restricted to JRE 1.3 • features • Divided in configurations, profiles • and optional APIs/JSRs 5

  6. Existence of Java ME • In the early 1990s, Sun Microsystems created a new programming • language called Oak with cross-platform support • Primary focus on small handheld device with an LCD touch-screen • and built-in wireless networking and infrared communications • Market was not ready • Internet market was booming now oak rename java • It was now divided into two group J2SE & J2EE • After a long time demand began to grow for Java on smaller devices • and even on smart cards, thus returning Java to its roots. • J2ME born later rename it as Java ME 6

  7. Advantage of Java ME • “Write Once, Run Anywhere” • Portability across the widest range of devices • Provide best solution for an extremely wide range of small device • Secure • Incorporation of high usability and value features • Easy to master 7

  8. Java ME Specification 8

  9. Configuration • At the heart of the Java ME platform is the configuration. A configuration defines a minimal Java runtime environment suitable for a certain class or family of devices. In particular, a configuration defines: • The capabilities of the Java virtual machine (VM) • The native code that interfaces with the underlying system • A set of Java runtime classes for running applications • Minimal device requirements for memory and input/output • mechanisms. 9

  10. How CLDC, CDC Configurations came into existence • Mobile phone , TV set-Top Boxes, Home appliances etc. having • Limited processing power • Limited graphical capability • Limited battery power • Lower power consumption • Limited memory • Working on intermittent connection and limited bandwidth • CDC targeted for? • JVM based devices • CLDC targeted for? • KVM based devices 10

  11. Connected Device Configuration • A subset of Java Standard Edition. • Contains almost all the libraries of Java SE except GUI related. • Optimized for multi-threaded low memory conditions. • 2 MB or more memory for Java platform • Four profiles are based on CDC: • Foundation Profile • Personal Basis Profile • Personal Profile • Gaming Profile • Designed for Mobile & Embedded Devices with higher • Processing Power, Memory and Display. • Current Release: CDC 1.1.2 (JSR 218) 11

  12. Connected Limited Device Configuration • 160 – 512K of memory available for Java. • Typically has limited power or battery operated. • Network connectivity, often wireless, intermittent, low - bandwidth. • Core Java class libraries available on a particular category of • devices.  • 32 kilobytes memory for runtime memory allocation. • Two profiles are based on CLDC: • Mobile Information Device Profile • Information Module Profile 12

  13. CLDC API Structure CLDC defines a core of APIs, mostly taken from the J2SE world. These include fundamental language classes in java.lang, stream classes from java.io, and simple collections from java.util. CLDC also specifies a generalized network API in javax.microedition.io.*; 13

  14. CLDC Core API 14

  15. Profile • A profile is layered on top of a configuration • It is a collection of Java based APIs that supplement a • Configuration to provide capabilities for a specific vertical market or • device type (for example, wireless: mobile devices, set-top box etc.). • The main goal for a profile is to provide flexibility to the Java • Community while still maintaining portability across device types. • Profiles are defined by open industry working groups (Samsung,Nokia, • Sony ericsson,LG etc.)utilizing the Java Community Process Program. • In this way industries can decide for themselves what elements are • necessary to provide a complete solution targeted at their industry. 15

  16. Profile • Profiles define the application life cycle model, the user interface, • and access to device specific properties. • Java ME Profiles: • Mobile Information Device Profile (MIDP) • PDA Profile (PDAP) • Foundation Profile (FP), • Personal Profile (PP) and Personal Basic Profile (PBP). • RMI Profile • Game Profile 16

  17. Java ME Family 17

  18. KVM • Sun's Kilobyte virtual machine • ~ 50K • With libraries + KVM ~130K • Designed from ground up to meet needs to mobile devices • Highly configurable but limits us because of size restrictions 18

  19. KVM Limitations • Doesn’t support float or double data types (CLDC 1.1 does) • java.util greatly reduced • Limited string, and I/O functionality • No JNI or custom class loaders • Change in classfile verification preverification 19

  20. KVM Limitations • java.lang subset and in some cases modified interface and • implementation signatures • Runtime - Reduced signature to memory operations - freeMemory(), gc(), totalMemory()) and exit() • System (reduced signature) • Threading –Thread groups or daemon threads • Provide ~8 K of data storing facility {RMS} • Unicode is supported, but far fewer encodings are supported 20

  21. One More Glance 21

  22. MIDP • MIDP stands for Mobile Information Device Profile. • MIDP combined with the Connected Limited Device • Configuration (CLDC), is the Java runtime environment for • today's mobile information devices (MIDs) such as phones and • set top box. • Provide Graphical User Interface • Currently MIDP 2.0/2.1 device in market • A keypad, keyboard, or touch screen • Two-way wireless networking capability • Media Support • Database support 22

  23. MIDP features • Externally triggered Java ME activation is supported { SMS , • MMS, CBS etc} • Access native services {dial tel number, open system browser etc} • User Interface • Multimedia access { playing tone, songs etc} • Gaming API • Network Connectivity 23

  24. MIDP Packages 24

  25. MIDP UI Library 25

  26. MIDlet • What is MIDlet ? • A MIDlet is a MID Profile application • javax.microedition.midlet.MIDlet; • The application must extend this class to allow the application • management software (AMS)to control the MIDlet • It Allows AMS to create, start, pause, and destroy a MIDlet javax.microedition.midlet.MIDlet; MyApp 26

  27. Application Management System • AMS software must work in conjunction with the device's native • system software • Control app lifecycle • Starting, Stopping & Pausing • KVM Control by AMS • Java ME app run under the control of KVM • AMS list all the installed MIDlet on the system • Task done by AMS Installation, Upgrade & Version management to • removal of application software 27

  28. AMS Action & MIDlet State 28

  29. MIDlet lifecycle 29

  30. MIDlet lifecycle • MIDlet belong to javax.microedition.midlet.*; package. • Every Java ME MIDlet based on three method • startApp • pauseApp • destroyApp • startApp method • The startApp method is called when the MIDlet is started. • After startApp has completed, the MIDlet is in Active state. • It check whether any elements have been set as the current • screen (Display). 30

  31. MIDlet lifecycle • pauseApp • MIDlet application start with pause state. • pauseApp call by external event like SMS, phone call etc. • destroyApp • When application wants to terminate MIDlet it calls destroyApp • MIDlet goes into the Destroyed state    • destroyApp method provides unconditional parameter • false MIDlet refuse to terminate • true AMS terminate the MIDlet • notifyDestroyed notifies the AMS that the MIDlet has entered • Destroyed state 31

  32. MIDlet lifecycle • MIDlet • import javax.microedition.midlet.MIDlet; • public class FirstMidlet extends MIDlet { • public void startApp() { • // MIDlet in Active State • } public void pauseApp() { • //MIDlet in Pause state • } public void destroyApp(boolean unconditional) { • //MIDlet in Destroyed state • } • } 32

  33. Hands On • Hands On try it your self 33

  34. Java ME Development Cycle • Writing the code • Using the text editor, enter source code, save the • code as <name>.java • Compiling the code • <name>.class • Pre-verification • <name>.class { increase size upto 5%} • Get JAD & JAR • Run MIDlet on device 34

  35. Java ME Development Cycle 35

  36. MIDlet Suite • The MIDlet suite is JAR & JAD file’s that contain one or more MIDlet • JAR=Java Archive File • JAD=Java Application Descriptor • The JAD makes information available to the application • manager. With this information, the manager can determine if the • device can accommodate the MIDlet 36

  37. Inside JAR • JSR is a production, packaged application generally consist of • many files. In addition to Java classes, other files such as images • and application data, known as resources, may be part of the • package. You bundle all this information together into a single entity, • a JAR file. 37

  38. Inside JAD • The JAD file provides information about the JAR, there are six • attributes that must be included into the JAD file. • Required six must JAD attributes: • MIDlet-Name -- Name of the MIDlet suite • MIDlet-Version -- Version number of the MIDlet • MIDlet-Vendor -- Who created the MIDlet • MIDlet-<n> -- Information about the MIDlet(s) in the suite • MIDlet-Jar-URL -- The URL of the JAR file • MIDlet-Jar-Size -- The size, in bytes, of the JAR • Optional attributes: • MIDlet-Description: • MIDlet-Delete-Confirm: • MIDlet-Install-Notify: 38

  39. Inside manifest • Reside inside the JAR file to provide the additional information about the JAR, there are six attributes that must be in the manifest file • Mandatory Attributes: • MIDlet-Name -- Name of the MIDlet suite • MIDlet-Version -- Version number of the MIDlet • MIDlet-Vendor -- Who created the MIDlet • MIDlet-<n> -- Information about MIDlet(s) in the suite • MicroEdition-Profile -- What profile is required by the MIDlet • MicroEdition-Configuration -- Configuration is required by the MIDlet • Optional attributes: • MIDlet-Icon: • MIDlet-Description: • MIDlet-Info-URL: Location 39

  40. Over the Air 40

  41. Over the Air • OTA is Over the Air provisioning, users acquire the jad/jar • as required via their browser • MIDP OTA Specification • – Device Functionality • Support for HTTP 1.0 or 1.1 • Discovery Application (to locate application and to • download) • AMS to manage OTA Application Provisioning life • cycle. 41

  42. J2ME MIDP packages • Application Lifecycle package • javax.microedition.midlet • User Interface package • javax.microedition.lcdui • Networking package • javax.microedition.io • Core packages • java.lang, java.io, java.util • Record Management Store • javax.microedition.rms 42

  43. lcdui package • MIDP UI is divided into two levels: the High-level and the • Low-level 43

  44. lcdui package 44

  45. lcdui package • User-interface classes in javax.microedition.lcdui (and • lcdui.games) • Device’s display is represented by an instance of Display. • Accessed from factory method getDisplay() • Display keeps track of what is currently visible, which is an • instance of Displayable • Current state of the screen is changed by passing • Displayable instances to Display’s setCurrent() method 45

  46. High Level UI • High-level API’s for high portability (Screen) • High – level MIDlet look and feel is same on all devices • No direct access to device features • Color, device inputs, screen size • Implementation provides interaction (scrolling, navigation, drawing) • Input key event handling is not available in high-level APIs by default. • The high-level APIs are: • Alert - A popup screen to notify the user about an event. • Form - A screen to which Form Items can be added. The Items are also considered high-level APIs. • List - A screen containing a scrollable list of choices. • TextBox - A screen in which the user can enter or edit text. 46

  47. Example • import javax.microedition.midlet.MIDlet; • import javax.microedition.lcdui.Display; • import javax.microedition.lcdui.Displayable; • import javax.microedition.lcdui.Command; • import javax.microedition.lcdui.CommandListener; • import javax.microedition.lcdui.Form; • public class HelloMidlet extends MIDlet implements CommandListener{ • private Form form = null; • private final Command cmdExit = new Command("Exit",Command.EXIT,1); • private final String name=“Hello World”; • public void startApp() { • form = new Form(name); • form.addCommand(cmdExit); • form.setCommandListener(this); • Display.getDisplay(this).setCurrent(form); • } • public void pauseApp() { • } • public void destroyApp(boolean unconditional) { • } • public void commandAction(Command c, Displayable d) { • destroyApp(true); • notifyDestroyed(); • } • } 47

  48. Event Handling • High Level Event Handling • Low Level Event Handling 48

  49. High Level Event Handling • Handling events in the high-level API is based on a listener model. • CommandListener Interface • ItemStateListener Interface • Command - The javax.microedition.lcdui.*; package provides the • Command class • Command(String label, intcommandType, int priority) 49

  50. High Level Event Handling • Command Type - The type specifies the command's intent. The defined • types are: BACK, CANCEL, EXIT, HELP, ITEM, OK, SCREEN, and STOP. • ... • Command exitCommand = new Command("Exit", Command. EXIT, 1); • Command backCommand = new Command("Back", Command. BACK, 1); • Command moreCommand = new Command("More", Command.SCREEN, 2); • ... 50

More Related