JABWT

Overview
The JABWT specification defines an optional package (javax.bluetooth) for Bluetooth wireless technology. Different implementations of JABWT exist for mobile devices (J2ME), and for PC's (J2SE). JABWT operates on top of the CLDC layer in the blutooth stack (same level as MIDP) and is intended to extend the capabilities of profiles like the MIDP. JABWT use the GCF, defined in the CLDC specification, for Bluetooth communication. JABWT consists of two packages. These packages are separate optional packages so the CLDC implementation may include either of the packages or both of them:  javax.bluetooth: The core Bluetooth API. provides an API for device discovery and service discovery. provides functionality for setting up services of your own and customization of local service records. Setting up L2CAP and RFCOMM connections is available through an extension to the GCF from the CLDC. javax.obex: The Object Exchange (OBEX) API.  

BCC
The device must have a Bluetooth Control Center (BCC) to which JABWT applications can direct their security requests. The BCC is the central authority for local Bluetooth device settings. A natural assumption is that the BCC relies on the Bluetooth security manager to carry out security related actions.

Getting Started
To get started, you need an implementation of the JABWT. Several implementations exist for desktops and for mobile devices. On Linux.Fedora for example, the "bluecove" implementation can be installed from the repository using the following command as root After that, you need to include the following two installed libraries in your Java class path: bluecove.jar and bluecove-gpl.jar

Device and Service Discovery
The following class is used to discover devices and their services.