C H A P T E R 1

Overview

This book describes how to port optional APIs that are part of the Java Wireless Client software. This book covers the optional APIs that do not belong wholly or partly to Sun Microsystems, Inc. The Optional APIs Porting Guide, Volume I covers optional APIs that do belong to Sun.

The exact porting process varies from API to API. In general, each optional API consists of three types of source code:

Java platform code

Platform-independent C code

Platform-dependent C code

The platform-independent C code is bound to some lower layer like PCSL and works as long as the lower layer is ported correctly.

The part you must port to use an optional API on your device is the platform-dependent code.

Some optional APIs are missing one or more types of source code. APIs that don't have any platform-dependent C code can be used "for free" without any porting.

If you are using the JavaCall trademark API, then no porting in the optional APIs themselves is necessary. All the platform-dependent C code is bound to the JavaCall API, which essentially makes it platform-independent C code. Your entire porting effort is concentrated on the JavaCall layer.

The following table lists the non-Sun optional APIs and their porting requirements:

Optional API	Porting Requirements
JSR 75	See Chapter 2.
JSR 82	See Chapter 3.
JSR 179	See Chapter 4.
JSR 180	The implementation is almost entirely Java platform code. Platform-independent C code hooks up the push registry. No porting is necessary.
JSR 205	This API (WMA 2.0) is already covered in Volume I of the Optional APIs Porting Guide in the chapter about WMA.
JSR 226	See Chapter 5.
JSR 229	The implementation consists of Java platform code and platform-independent C code. No porting is necessary.
JSR 238	See Chapter 6.