package-summary.html

是MIDP 的API 查詢文件, 大家可以看一下裡面的index.html, 再用Package 或 Class 名字來查.

        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            The description of the MIDlet suite.</P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            MIDlet-Info-URL</P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            A URL for information further describing the MIDlet suite.
            The syntax and meaning MUST conform to RFC2396 and RFCs that
            define each scheme.</P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            MIDlet-&lt;n&gt;</P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            The name, icon, and class of the nth MIDlet in the JAR file separated
            by a comma. The lowest value of &lt;n&gt; MUST be 1 and consecutive
            ordinals MUST be used. 
	    The first missing entry terminates the list.
	    Any additional entries are ignored.
	    Leading and trailing spaces in
            name, icon and class are ignored.  
	  </P>
          <OL>
            <LI>
              Name is used to identify this MIDlet to the user.
              The name must be present and be non-null.</LI>
            <LI>
              Icon is the case-sensitive absolute path name of an
              image (PNG) within the JAR for the icon of the nth
              MIDlet.  The icon may be omitted.</LI>
            <LI>
              Class is the name of the class extending the
              <CODE>javax.microedition.midlet.MIDlet</CODE> class for
              the nth MIDlet. The classname MUST be non-null and
              contain only characters for Java class names.  The class
              MUST have a public no-args constructor. The class name
              IS case sensitive.</LI>
          </OL>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            MIDlet-Jar-URL</P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            The URL from which the JAR file can be loaded.  The syntax
            and meaning MUST conform to RFC2396 and RFCs that define
            each scheme. Both absolute and relative URLs MUST be
            supported. The context for a relative URL is the URL from
            which this application descriptor was loaded.</P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            MIDlet-Jar-Size</P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            The number of bytes in the JAR file.</P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            MIDlet-Data-Size</P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            The minimum number of bytes of persistent data required by the MIDlet.
            The device may provide additional storage according to its own policy.
            The default is zero.</P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            MicroEdition-Profile</P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>The J2ME profiles required, using the same format and
          value as the System property
          <CODE>microedition.profiles</CODE> (for example "MIDP-2.0").
          The device must implement <EM>all</EM> of the profiles
          listed.  If any of the profiles are not implemented the
          installation MUST fail.  Multiple profiles are separated
          with a blank (Unicode U+0020).</P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            MicroEdition-Configuration</P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            The J2ME Configuration required using the same format and value as the
            System property <CODE>microedition.configuration</CODE>
            (for example &quot;CLDC-1.0&quot;).</P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>MIDlet-Permissions
            </P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>Zero or more permissions that are critical to the function
            of the MIDlet suite.
            See the <A HREF="doc-files/Authorization.html">MIDlet Suite
            Security</A> section for details of usage.
          </P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>MIDlet-Permissions-Opt
            </P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>Zero or more permissions that are non-critical to the
            function of the MIDlet suite.
            See the <A HREF="doc-files/Authorization.html">MIDlet Suite
            Security</A> section for details of usage.
          </P>
        </TD>
      </TR>
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>MIDlet-Push-&lt;n&gt;
          </P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>
            Register a MIDlet to handle inbound connections.
            Refer to <A HREF="../io/PushRegistry.html">
              javax.microedition.io.PushRegistry</A> for details.
          </P>
        </TD>
      </TR>

      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>MIDlet-Install-Notify
          </P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>Refer to the <A HREF="../../../../OTASpecification.html#AdditionalAttributes">
                        OTA Specification</A> for details.
          </P>
        </TD>
      </TR>

      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>MIDlet-Delete-Notify
          </P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>Refer to the <A HREF="../../../../OTASpecification.html#AdditionalAttributes">
                        OTA Specification</A> for details.
          </P>
        </TD>
      </TR>

      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>MIDlet-Delete-Confirm
          </P>
        </TD>
        <TD ROWSPAN="1" COLSPAN="1">
          <P>Refer to the <A HREF="../../../../OTASpecification.html#AdditionalAttributes">
                        OTA Specification</A> for details.
          </P>
        </TD>
      </TR>

    </TABLE>

   <P>
     Some attributes use multiple values, for those attributes the
     values are separated by a comma (Unicode U+002C) except where noted.
     Leading and trailing whitespace (Unicode U+0020) and tab
     (Unicode U+0009) are ignored on each value. </P>


    <H4><A NAME="vernum">Version Numbering</A></H4>
    <P>
      Version numbers have the format Major.Minor[.Micro] (X.X[.X]), where
      the .Micro portion MAY be omitted. (If the .Micro portion is not
      omitted, then it defaults to zero). In addition, each portion of the
      version number is allowed a maximum of two decimal digits (i.e.,
      0-99).
      Version numbers are described in the
      the Java(TM) Product Versioning Specification
      <A HREF="http://java.sun.com/products/jdk/1.2/docs/guide/versioning/spec/VersioningSpecification.html">
        http://java.sun.com/products/jdk/1.2/docs/guide/versioning/spec/VersioningSpecification.html</A>.</P>
    <P>
      For example, 1.0.0 can be used to specify the first version of a MIDlet
      suite. For each portion of the version number, leading zeros are not
      significant. For example, 08 is equivalent to 8. Also, 1.0 is
      equivalent to 1.0.0. However, 1.1 is equivalent to 1.1.0, and not
      1.0.1.</P>
    <P>
      A missing MIDlet-Version tag is assumed to be 0.0.0, which means that
      any non-zero version number is considered as a newer version of the
      MIDlet suite.</P>
    
    <H4>JAR Manifest</H4>
    <P>
      The manifest provides information about the contents of the JAR file.
      JAR file formats and specifications are available at 
      <A
        HREF="http://java.sun.com/products/jdk/1.2/docs/guide/jar/index.html">
        http://java.sun.com/products/jdk/1.2/docs/guide/jar/index.html.</A>
      Refer to the JDK JAR and manifest documentation for the syntax and
      related details. MIDP implementations MUST implement handling of
      lines longer than 72 bytes as defined in the manifest
      specification.
      An attribute MUST not appear more than once within the manifest.
      If an attribute is duplicated the effect is unspecified.
      Manifest attributes are passed to the MIDlet when requested
      using the <CODE>MIDlet.getAppProperty</CODE> method, unless the
      attribute is duplicated in the application descriptor, for
      handling of duplicate attributes see the "Application
      Descriptor" section.</P>

    <P>
      The manifest MUST contain the following attributes:</P>
    <UL>
      <LI>
        MIDlet-Name</LI>
      <LI>
        MIDlet-Version</LI>
      <LI>
        MIDlet-Vendor</LI>
    </UL>
    <P>
      The manifest or the application descriptor MUST contain the following
      attributes:</P>
    <UL>
      <LI>
        MIDlet-&lt;n&gt; for each MIDlet</LI>
      <LI>
        MicroEdition-Profile</LI>
      <LI>
        MicroEdition-Configuration</LI>
    </UL>
    <P>
      The manifest MAY contain the following:</P>
    <UL>
      <LI>
        MIDlet-Description</LI>
      <LI>
        MIDlet-Icon</LI>
      <LI>
        MIDlet-Info-URL</LI>
      <LI>
        MIDlet-Data-Size</LI>
      <LI>
        MIDlet-Permissions </LI>
      <LI>
        MIDlet-Permissions-Opt </LI>
      <LI>
	MIDlet-Push-&lt;n&gt;</LI>
      <LI>
        MIDlet-Install-Notify</LI>
      <LI>
        MIDlet-Delete-Notify</LI>
      <LI>
        MIDlet-Delete-Confirm </LI>
      <LI>
	Any application-specific attributes that do not begin with
	<CODE>MIDlet-</CODE> or <CODE>MicroEdition-</CODE></LI>
    </UL>

    <P>
      For example, a manifest for a hypothetical suite of card games would
      look like the following example:</P>
    <TABLE BORDER="2" width="400">
      <TR>
        <TD ROWSPAN="1" COLSPAN="1">
          <pre><code>
  MIDlet-Name: CardGames    
  MIDlet-Version: 1.1.9    
  MIDlet-Vendor: CardsRUS    
  MIDlet-1: Solitaire, /Solitare.png, org.cardsrus.games.Solitare     
  MIDlet-2: JacksWild, /JacksWild.png, org.cardsrus.games.JacksWild     
  MicroEdition-Profile: MIDP-2.0     
  MicroEdition-Configuration: CLDC-1.0     
  Solitaire-Author: John Q. Public      </CODE></PRE>
        </TD>
      </TR>
    </TABLE>
    
    
    <H4> MIDlet Classes</H4>
    <P>
      All Java classes needed by the MIDlet are be placed in the JAR file
      using the standard structure, based on mapping the fully qualified
      class names to directory and file names. Each period is converted to a
      forward slash ( / ) and the <CODE>.class</CODE>
      extension is appended. For example, a class 
      <CODE>com.sun.microedition.Test</CODE>
      would be placed in the JAR file with the name 
      <CODE>com/sun/microedition/Test.class</CODE>
      .</P>
    
    
    
    <H3>Application Descriptor</H3>
    <P>
      Each JAR file MAY be accompanied by an application descriptor. 
      The application descriptor is used in conjunction with the JAR
      manifest by the application management software to manage the MIDlet and
      is used by the MIDlet itself for configuration specific attributes. The
      descriptor allows the application management software on the device to
      verify that the MIDlet is suited to the device before loading the full
      JAR file of the MIDlet suite. It also allows configuration-specific
      attributes (parameters) to be supplied to the MIDlet(s) without
      modifying the JAR file.</P>
    <P>
      To allow devices to dispatch an application descriptor to the MIDP
      application management software, a file extension and
      <A HREF="http://www.iana.org/assignments/media-types/text/vnd.sun.j2me.app-descriptor">
        MIME type</A> are registered with the IANA:</P>
    <UL>