When Bluetooth is disabled a RuntimeException is thrown instead of BluetoothStateException about bluecove

[GoogleCodeExporter]

related problem:

> I'm writing to you to signal a little bit surprising behaviour of my version
> of BlueCove (a SNAPSHOT of the beginning of August..) with WIDCOMM drivers
> on Windows XP:
> (that's what i tried, i don't know the behaviour with different operating
> systems... but i found that only with WIDCOMM drivers on XP..):
> when the bluetooth is off, a call to Connector.open with a server connection
> string doesn't throw any exception! The exception is only thrown if you call
> acceptAndOpen or updateRecord on the ConnectionNotifier returned from the
> Connector...
> I'm signaling you this because that's a difference of behaviour with the
> other types of drivers (with XP-sp2 and BlueSoleil the VM can't load the
> implementation class..), and then a programmer would have to consider it
> (and would have to known it!) while handling the exceptions...

> Greetings and smiles,
> Fabrizio. 

Original comment by [email protected] on 9 Sep 2007 at 5:33

• Changed state: Accepted

[GoogleCodeExporter]

Made initial refactoring for the use of the reference to used BluetoothStack.
Now BluetoothStateException is thrown when required.

Original comment by [email protected] on 5 Oct 2007 at 2:18

[GoogleCodeExporter]

fixed initialization exceptions, e.g. BluetoothStateException when device is not
ready or no stack found

Original comment by [email protected] on 5 Oct 2007 at 3:55

• Changed state: Fixed