 |
del.icio.us |
 |
Digg |
 |
Furl |
 |
|
 |
Rojo |
| Add to OnlyWire |
 |
|
| Java Card | |
|---|---|
| Micro Edition (ME) | |
| Standard Edition (SE) | |
| Enterprise Edition (EE) |
In computing, the Java Platform, Micro Edition or Java ME (still commonly referred to by its previous name: Java 2 Platform, Micro Edition or J2ME) is a specification of a subset of the Java platform aimed at providing a certified collection of Java APIs for the development of software for tiny, small and resource-constrained devices based on microcontrollers such as ARM7, ARM9, AVR32, ... Target devices are from many industries: Home appliances, Security, Defense, Automotive, Industrial, Handsets, Industrial Control, Multimedia, Communication, ... cell phones , PDAs and set-top boxes are some well known samples.
Java ME was designed by Sun Microsystems and is a replacement for a similar technology, PersonalJava. Originally developed under the Java Community Process as JSR 68, the different flavors of Java ME have evolved in separate JSRs. Sun provides a reference implementation of the specification, but has tended not to provide free binary implementations of its Java ME runtime environment for mobile devices, rather relying on third parties to provide their own.
As of 22 December 2006, the Java ME source code is licensed under the GNU General Public License, and is released under the project name phoneME.
Contents |
Usage
Java ME has become a popular option for creating games for cell phones, as they can be emulated on a PC during the development stage and easily uploaded to phones. This contrasts with the difficulty of developing, testing, and loading games for other special gaming platforms such as those made by Nintendo, Sony, Microsoft, and others, as expensive system-specific hardware and kits are required.
Java ME devices implement a profile. The most common of these are the Mobile Information Device Profile aimed at mobile devices, such as cell phones, and the Personal Profile aimed at consumer products and embedded devices like Set-top boxes and PDAs.
Profiles are subsets of configurations, of which there are currently two: the Connected Limited Device Configuration and the Connected Device Configuration.
Connected Limited Device Configuration
The Connected Limited Device Configuration (CLDC) contains a strict subset of the Java-class libraries, and is the minimal amount needed for a Java virtual machine to operate. CLDC is basically used to classify myriad devices into a fixed configuration.
A configuration provides the most basic set of libraries and virtual-machine features that must be present in each implementation of a J2ME environment. When coupled with one or more profiles, the Connected Limited Device Configuration gives developers a solid Java platform for creating applications for consumer and embedded devices.
Mobile Information Device Profile
Designed for cell phones, the Mobile Information Device Profile includes a GUI API, and MIDP 2.0 includes a basic 2D gaming API. Applications written for this profile are called MIDlets. Almost all new cell phones come with a MIDP implementation, and it is now the de facto standard for downloadable cell phone games. However, many cellphones can run only those MIDlets that have been approved by the carrier, especially in North America[citation needed].
JSR 271: Mobile Information Device Profile 3 will specify the 3rd generation Mobile Information Device Profile (MIDP3), expanding upon the functionality in all areas as well as improving interoperability across devices. A key design goal of MIDP3 will be backward compatibility with MIDP2 content.
Information Module Profile
The Information Module Profile (IMP) is a profile for embedded, "headless" devices such as vending machines, industrial embedded applications, security systems, and similar devices with either simple or no display and with some limited network connectivity.
Originally introduced by Siemens Mobile and Nokia as JSR-195, IMP 1.0 is a strict subset of MIDP 1.0 except that it doesn't include user interface APIs — in other words, it doesn't include support for the Java package javax.microedition.lcdui. JSR-228, also known as IMP-NG, is IMP's next generation that is based on MIDP 2.0, leveraging MIDP 2.0's new security and networking types and APIs, and other APIs such as PushRegistry and platformRequest(), but again it doesn't include UI APIs, nor the game API.
Connected Device Configuration
The Connected Device Configuration is a subset of Java SE, containing almost all the libraries that are not GUI related. It is richer than CLDC.
Foundation Profile
The Foundation Profile is a Java ME Connected Device Configuration (CDC) profile. This profile is intended to be used by devices requiring a complete implementation of the Java virtual machine up to and including the entire Java Platform, Standard Edition API. Typical implementations will use some subset of that API set depending on the additional profiles supported. This document describes the facilities that the Foundation Profile provides to the device and other profiles that use it. This specification was developed under the Java Community Process.
Personal Basis Profile
The Personal Basis Profile extends the Foundation Profile to include lightweight GUI support in the form of an AWT subset.
Personal Profile
The Personal Profile is an extension of the Personal Basis Profile, and includes a more comprehensive AWT subset and adds applet support.
Implementations
Sun provides a reference implementation of the specification.
In contrast to the numerous binary implementations of the Java Platform Sun provides on server and workstation machines, Sun does not usually provide binaries for the platforms of Java ME targets. One notable omission is for Microsoft Windows Mobile (Pocket PC) based devices, despite an open-letter campaign to Sun to release a rumoured complete project "Captain America" which is such an implementation.[1]
Operating systems targeting Java ME have been implemented by DoCoMo in the form of DoJa, and by SavaJe as SavaJe OS. The latter company was purchased by Sun in April 2007 and now forms the basis of Sun's JavaFX Mobile. The company www.ist-eu.com[2] provides Java ME virtual machine (MicroJvm), qualified as baremetal, where the virtual machine is the OS/RTOS: the device boots in Java.
Getting Started
Netbeans, a free open-source Integrated Development Environment that runs in any operating systems, enables software developers to create, test, debug and deploy applications that will run on mobile phones, PDAs, set-top boxes, embedded systems.
Required Software
Java SE Development Kit (JDK 6 Update 7)[1]
Netbeans 6.1 IDE (Mobility bundle)[2]
If you already have Netbeans installed, please check that you have both the Mobility pack and CDC Java ME plugins installed.
In Netbeans, Tools >> Plugins >> Installed tab
Mobile Emulators / SDK
You can download and install the following SDK so that you can develop your mobile applications for the targeted platforms.
Adding Platforms
After downloading the required emulators and SDKs, it is time to integrate them into the Netbeans IDE.
1. From the Netbeans menu -> Tools, select Java Platforms.
Java Platform Manager window will appear.
2. Click on Add Platform.. button.
Add Java Platform window will appear.
3. Select Java ME MIDP Platform Emulator for CLDC platforms or Java ME CDC Platform Emulator for CDC platforms.
4. Click Next.
The list of detected platforms will be displayed. If your platform is not detected automatically, click on Find more Java ME Platform Folders... to locate the folder the SDK is installed to.
5. Select the platforms that you wish to install.
6. Click Next.
7. Click Finish.
You will be able to see the newly installed platform under your Java Platform Manger window.
Windows Mobile
There are additional steps to be performed before the emulator for Windows Mobile can be integrated into Netbeans.
[--TO FILL--]
Creating your First Project
[-- TO FILL --]
Troubleshooting
[-- TO FILL --]
JSRs
Foundation
| JSR # | Name | Description |
|---|---|---|
| 30 | CLDC 1.x | |
| 37 | MIDP 1.0 | |
| 118 | MIDP 2.x | |
| 139 | CLDC 1.1 |
Future
| JSR # | Name | Description |
|---|---|---|
| 271 | MIDP 3.0 |
Main Extensions
| JSR # | Name | Description |
|---|---|---|
| 75 | File Connection and PIM | |
| 82 | Bluetooth | |
| 120 | Wireless Messaging API (WMA) | |
| 135 | Mobile Media API (MMAPI) | Audio, video, multimedia |
| 172 | Web Services | |
| 177 | Security and Trust Services | |
| 179 | Location API | |
| 180 | SIP API | |
| 184 | Mobile 3D Graphics | |
| 185 | Java Technology for the Wireless Industry (JTWI) | General |
| 205 | Wireless Messaging 2.0 (WMA) | |
| 211 | Content Handler API | |
| 226 | SVG 1.0 | |
| 229 | Payment API | |
| 234 | Advanced Multimedia Supplements (AMMS) | MMAPI extensions |
| 238 | Mobile Internationalization API | |
| 239 | Java Bindings for the OpenGL ES API | |
| 248 | Mobile Service Architecture | General |
| 256 | Mobile Sensor API | |
| 287 | SVG 2.0 |
See also
Notes
References
- JSR 232: Mobile Operational Management An advanced OSGi technology based platform for mobile computing
- JSR 291: Dynamic Component Support for Java SE - Symmetric programming model for Java SE to Java ME JSR 232
External links
- Sun Developer Network, Java ME
- Nokia's Developer Hub
- Sony Ericsson Developer World
- Motorola Developer Network
- Samsung Mobile Developer's site
- Sprint Application Developer's Website
- Performance database of Java ME compatible devices
- Microjava.com
|
|||||||||||||||||||||||||
Article keywords: java programming, sun java, java development,
