MOBILE JAVA: PACKAGE-READING EXERCISE
Yenra | Reviewed October 12, 2026
Companion guide: https://yenra.com/mobile-java/

This is an original fictional study example, not an installable application.
No JAR archive or compiled entry class is supplied. All archive sizes below
are illustrative bytes, not kilobytes.

DESCRIPTOR EXAMPLE
MIDlet-Name: PocketNote
MIDlet-Version: 1.0.0
MIDlet-Vendor: Yenra
MIDlet-1: PocketNote,,org.yenra.demo.PocketNote
MicroEdition-Configuration: CLDC-1.1
MicroEdition-Profile: MIDP-2.0
MIDlet-Jar-URL: pocketnote.jar
MIDlet-Jar-Size: 4096

QUESTIONS
1. Which configuration and profile does this suite declare?
2. What does the empty field between two commas in MIDlet-1 represent?
3. Is pocketnote.jar an absolute web address?
4. A rebuilt JAR contains 4,200 bytes. How far is the descriptor size off?
5. What should be checked besides the JAR filename and its size?
6. Does changing MIDP-2.0 to MIDP-1.0 supply missing platform APIs?

ANSWERS
1. CLDC 1.1 and MIDP 2.0. Compare these with the exact device runtime.
2. The optional icon field is empty. The final field names the entry class.
3. No. In this example it is resolved relative to the descriptor location.
4. 4,200 - 4,096 = 104 bytes. Update the record to the actual build length.
5. Compare suite identity with the manifest; confirm the entry class and
   resources exist; check optional APIs, device limits, permissions and any
   external services needed by the real application.
6. No. A textual requirement change does not implement absent APIs.

RECORD YOUR OWN INSPECTION
Exact device/runtime:
CLDC/MIDP versions:
JAR filename and actual byte length:
Declared byte length:
Entry class and resource checks:
Optional APIs:
Permissions/signing policy:
Server or account dependencies:
Observed result (installation, launch, offline task, online task):

Read the companion guide for sources and context. Preserve original package
files before investigating a copy. This exercise makes no claim of testing
an application on real phone hardware.