Persistent Storage II: File Connection and PIM API - Beginning J2ME: From Novice to Professional - page 140

public void pauseApp() {}
public void destroyApp(boolean flg) {
}
public void commandAction(Command c, Displayable s) {
if (c == mExitCommand) {
destroyApp(true);
notifyDestroyed();
}
}
public void verifyPIMSupport() throws IOException {
String version = null;
version = System.getProperty("microedition.pim.version");
if (version != null) {
if (!version.equals("1.0"))
throw new IOException("Package is not version 1.0.");
}
else
throw new IOException("PIM optional package is not available.");
}
}
In the constructor, notice the use of the items() method of the ContactList to obtain an
Enumeration of contacts. The Contact.NAME_GIVEN and Contact.NAME_FAMILY subfields of the
Contact.NAME field are then extracted and displayed in a GUI list.
Summary
JSR 75 specifies two optional packages for persistent storage beyond the record store mechanism of
MIDP.
The File Connection Optional Package exposes an API that can be used by applications to
access a device's file systems. These file systems typically correspond to a flash memory card
that can be added or removed at any time. A centralized file system registry that tracks the
addition and removal of file systems is available to applications using the FileConnection API.
The PIM Optional Package enables applications to access PIM databases. These databases
are typically created and maintained by native PIM applications. You can add, modify, or delete
records contained in contacts, events, and to-do lists. PIM applications across different devices
may maintain different data fields. The API handles these differences by mapping to a standard
set of fields, selected from the vCard and vCalendar personal data interchange specifications
from the Internet Email Consortium.