The expert group that defined JABWT consisted of
18 companies and three individuals. The companies were Extended
Systems, IBM, Mitsubishi Electric, Motorola, Newbury Networks, Nokia,
Parthus Technologies, Research in Motion, Rococo Software, Sharp
Laboratories of America, Sony Ericsson Mobile Communications, Smart
Fusion, Smart Network Devices, Sun Microsystems, Symbian, Telecordia,
Vaultus, and Zucotto. The API was defined as an optional package for
Java ME devices based on CLDC.
1.5.2 What about Java SE?
Because Bluetooth wireless technology can be found in Java SE devices,
you may ask why this standardization effort focused on Java ME devices.
The expert group believed that the initial set of devices that would use
Java language capabilities over Bluetooth protocols would be in the Java
ME device space. However, as the next chapters show, the API was
defined in such a way as to rely heavily on one set of CLDC APIs
known as the Generic Connection Framework (GCF).
20 Chapter One: Introduction
That thinking partially paid off. JSR-197 (Generic Connection Framework
Optional Package) [23] defined the GCF for Java SE. Those Java
SE platforms that include JSR-197 may support JABWT in the future.
1.6 Summary
The JABWT specification provides a standard set of APIs for developing
Bluetooth applications.
Pages:
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60