overview.html

J2ME MIDP2.0 final specification

	Limited Device Configuration 1.1 (JSR-139), Sun Microsystems,
	Inc</a>.</li>
    </ul>

    <h3 class="SectionTitle">Report and Contact</h3>
    <p class="Paragraph">
      Your comments on this specification are welcome and
      appreciated. Please send your comments to:</p>
    <p class="Paragraph">
      <em class="Code"><a href="mailto:[e-mail]">[e-mail]</a></em></p>

    <a name="Definitions"></a>
    <h3 class="SectionTitle">Definitions</h3>
    <p class="Paragraph">
      This document uses definitions based upon those specified in <a
      href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>.
    </p>
    <br><b>Specification Terms</b>
    <table class="Table" border="1" cellpadding="3">
    <tr>
      <th rowspan="1" colspan="1">
	<p class="TableHead">Term</p>
      </th>
      <th rowspan="1" colspan="1">
	<p class="TableHead">
	  Definition</p>
      </th>
    </tr>
    <tr>
      <td rowspan="1" colspan="1">
	<p class="TableText">MUST</p>
      </td>
      <td rowspan="1" colspan="1">
	<p class="TableText">The associated definition is an absolute
	requirement of this specification.</p>
      </td>
    </tr>
    <tr>
      <td rowspan="1" colspan="1">
	<p class="TableText">MUST NOT</p>
      </td>
      <td rowspan="1" colspan="1">
	<p class="TableText">The definition is an absolute prohibition
	of this specification.</p>
      </td>
    </tr>
    <tr>
      <td rowspan="1" colspan="1">
	<p class="TableText">SHOULD</p>
      </td>
      <td rowspan="1" colspan="1">
	<p class="TableText">Indicates a recommended practice. There
	may exist valid reasons in particular circumstances to ignore
	this recommendation, but the full implications must be
	understood and carefully weighed before choosing a different
	course.</p>
      </td>
    </tr>
    <tr>
      <td rowspan="1" colspan="1">
	<p class="TableText">SHOULD NOT</p>
      </td>
      <td rowspan="1" colspan="1">
	<p class="TableText">Indicates a non-recommended
	practice. There may exist valid reasons in particular
	circumstances when the particular behavior is acceptable or
	even useful, but the full implications should be understood
	and the case carefully weighed before implementing any
	behavior described with this label.</p>
      </td>
    </tr>
    <tr>
      <td rowspan="1" colspan="1">
	<p class="TableText">MAY</p>
      </td>
      <td rowspan="1" colspan="1">
	<p class="TableText">Indicates that an item is truly optional.</p>
      </td>
    </tr>
  </table>

    <h3 class="SectionTitle">Contributors</h3>
    <p class="Paragraph">
      This specification was produced by the JSR-118 Expert Group, as
      a part of the Java Community Process. The following companies
      and individuals, listed in alphabetical order, were members of
      the Expert Group:</p>
    <ul>
      <li class="Bullet1">
	Companies:
	<ul>
	  <li class="Bullet2">
	    4thpass Inc</li>
	  <li class="Bullet2">
	    AGEA Corporation</li>
	  <li class="Bullet2">
	    Alcatel</li>
	  <li class="Bullet2">
	    Aplix Corporation</li>
	  <li class="Bullet2">
	    AromaSoft Corp</li>
	  <li class="Bullet2">
	    Baltimore Technologies</li>
	  <li class="Bullet2">
	    CELLon France</li>
	  <li class="Bullet2">
	    Distributed Systems Technology Centre</li>
	  <li class="Bullet2">
	    Elata PLC</li>
	  <li class="Bullet2">
	    Esmertec</li>
	  <li class="Bullet2">
	    Espial Group Inc</li>
	  <li class="Bullet2">
	    France Telecom / Orange</li>
	  <li class="Bullet2">
	    Fujitsu Limited</li>
	  <li class="Bullet2">
	    German Aerospace Center (DLR), Institute of Communications and Navigation </li>
	  <li class="Bullet2">
	    Hitachi Ltd./Digital Media Group</li>
	  <li class="Bullet2">
	    In Fusio</li>
	  <li class="Bullet2">
	    J-PhoneEast Co. Ltd</li>
	  <li class="Bullet2">
	    Logica Mobile Networks</li>
	  <li class="Bullet2">
	    Mitsubishi Electric Corp</li>
	  <li class="Bullet2">
	    Mobile Scope AG</li>
	  <li class="Bullet2">
	    Mobilitec</li>
	  <li class="Bullet2">
	    Motorola</li>
	  <li class="Bullet2">
	    NEC Corporation</li>
	  <li class="Bullet2">
	    Nextel Communications Inc</li>
	  <li class="Bullet2">
	    Nokia</li>
	  <li class="Bullet2">
	    NTT DoCoMo, Inc</li>
	  <li class="Bullet2">
	    Omnitel Pronto Italia S.p.A</li>
	  <li class="Bullet2">
	    One 2 One</li>
	  <li class="Bullet2">
	    Openwave Systems, Inc</li>
	  <li class="Bullet2">
	    Orange (UK)</li>
	  <li class="Bullet2">
	    Palm</li>
	  <li class="Bullet2">
	    Philips Consumer Communications</li>
	  <li class="Bullet2">
	    Philips Semiconductors</li>
	  <li class="Bullet2">
	    Research In Motion (RIM)</li>
	  <li class="Bullet2">
	    Samsung Electronics Co., Ltd</li>
	  <li class="Bullet2">
	    Sharp Labs</li>
	  <li class="Bullet2">
	    Siemens AG</li>
	  <li class="Bullet2">
	    Siemens ICM</li>
	  <li class="Bullet2">
	    Smart Fusion</li>
	  <li class="Bullet2">
	    Sony Ericsson Mobile Communications</li>
	  <li class="Bullet2">
	    Sun Microsystems, Inc</li>
	  <li class="Bullet2">
	    Symbian Ltd</li>
	  <li class="Bullet2">
	    Telef髇ica M髒iles Espa馻</li>
	  <li class="Bullet2">
	    Vaultus, Inc</li>
	  <li class="Bullet2">
	    Veloxsoft, Inc</li>
	  <li class="Bullet2">
	    Vodafone Global Platform &amp; Internet Services</li>
	  <li class="Bullet2">
	    Vodafone Group Services Limited</li>
	  <li class="Bullet2">
	    Vodafone Multimedia</li>
	  <li class="Bullet2">
	    Zucotto Wireless</li>
	</ul> 
      </li>
    <li class="Bullet1">
      Individuals:
      <ul>
	<li class="Bullet2">
	  Fabio Ciucci</li>
	<li class="Bullet2">
	  Glen Cordrey</li>
	<li class="Bullet2">
	  Jon Eaves</li>
	<li class="Bullet2">
	  David Hook</li>
	<li class="Bullet2">
	  Myank Jain</li>
	<li class="Bullet2">
	  Neil Katin</li>
	<li class="Bullet2">
	  Steve Ma</li>
	<li class="Bullet2">
	  Ravi Reddy</li>
	<li class="Bullet2">
	  Wai Kit Tony Fung</li>
      </ul>
    </li>
  </ul>

<hr>
    <h3 class="SectionTitle">Introduction</h3>
    <p class="Paragraph">
      This document, produced as a result of Java Specification
      Request (JSR) 118, defines the Mobile Information Device Profile
      (MIDP) v2.0 for the Java 2 Platform, Micro Edition
      (J2ME<sup><font size=-2>TM</font></sup>). The goal of this
      specification is to define an enhanced architecture and the
      associated APIs required to enable an open, third-party,
      application development environment for mobile information
      devices, or MIDs.</p>
    <p class="Paragraph">
      The MIDP 2.0 specification is based on the MIDP 1.0
      specification and provides backward compatibility with MIDP 1.0
      so that MIDlets written for MIDP 1.0 can execute in MIDP 2.0
      environments.
    <p class="Paragraph">
      The MIDP is designed to operate on top of the Connected, Limited
      Device Configuration (CLDC) which is described in <a
      href="http://jcp.org/jsr/detail/30.jsp"><em>Connected,
      Limited Device Configuration (JSR-30)</em></a>, Sun
      Microsystems, Inc. While the MIDP 2.0 specification was designed
      assuming only CLDC 1.0 features, it will also work on top of <a
      href="http://jcp.org/jsr/detail/139.jsp"><em>CLDC 1.1
      (JSR-139)</em></a>, and presumably any newer versions. It is
      anticipated that most MIDP 2.0 implementations will be based on
      CLDC 1.1.</p>

    <h3 class="SectionTitle">Scope</h3>
    <p class="Paragraph">
      Mobile Information Devices (MIDs) span a potentially wide set of
      capabilities. Rather than try to address all such capabilities,
      the MIDP 1.0 (JSR-037) and MIDP 2.0 (JSR-118) expert groups
      agreed to limit the set of APIs specified, addressing only those
      functional areas that were considered absolute requirements to
      achieve broad portability and successful deployments. These
      include:</p>
    <ul>
      <li class="Bullet1">
	Application delivery and billing</li>
      <li class="Bullet1">
	Application lifecycle (i.e., defining the semantics of a MIDP
	application and how it is controlled)</li>
      <li class="Bullet1">
	Application signing model and privileged domains security
	model</li>
      <li class="Bullet1">
	End-to-end transactional security (https)</li>
      <li class="Bullet1">
	MIDlet push registration (server push model)</li>
      <li class="Bullet1">
	Networking</li>
      <li class="Bullet1">
	Persistent storage</li>
      <li class="Bullet1">
	Sound</li>
      <li class="Bullet1">
	Timers</li>
      <li class="Bullet1">
	User interface (UI) (including display and input, as well as
	the unique requirements for games).</li>
    </ul>
    <p class="Paragraph">
      The above features are discussed in more depth in the associated
      <a href="javadoc/index.html">Javadoc</a>.</p>
    <p class="Paragraph">
      By the same reasoning, some areas of functionality were
      considered to be outside the scope of the MIDP. These areas
      include:</p>
    <ul>
      <li class="Bullet1">
	System-level APIs: The emphasis on the MIDP APIs is, again, on
	enabling application programmers, rather than enabling system
	programming. Thus, low-level APIs that specify a system
	interface to, for example, a MID's power management or voice
	CODECs are beyond the scope of this specification.</li>
      <li class="Bullet1">
	Low-level security: The MIDP specifies no additional low-level
	security features other than those provided by the CLDC. </li>
    </ul>

    <h3 class="SectionTitle">Architecture</h3>
    <p class="Paragraph">
      This section addresses issues that both implementers and
      developers will encounter when implementing and developing
      MIDP. While not comprehensive, this chapter does reflect the
      most important issues raised during deliberations of the
      MIDP Expert Group (MIDPEG).</p>
    <p class="Paragraph">
      As stated before, the goal of the MIDP is to create an open,
      third-party application development environment for MIDs. In a
      perfect world, this specification would only have to address
      functionality defined by the MIDP specification. In reality,
      most devices that implement the MIDP specification will be, at
      least initially, devices that exist on the market today. The <a
      href="#ArchFig">High-Level Architecture</a> shows a high-level