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 belong wholly or partly to Sun Microsystems, Inc. Volume II of the Optional APIs Porting Guide covers optional APIs that do not belong to Sun. You receive Volume II only if you have the corresponding product bundle.

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 Sun optional APIs and their porting requirements:

Optional API	Porting Requirements
JSR 120 and JSR 205	See Chapter 2
JSR 135	See Chapter 3
JSR 172	The implementation consists entirely of Java platform code. No porting is necessary.
JSR 177	See Chapter 4
JSR 211	See Chapter 5
JSR 239	See Chapter 6