Aktuelle Java Projekte

JTAPI-TAPI-Bridge Bug Parade

These are the kown bugs in my implementation:

ID Synopsis Current State Last Modified

1.1.0-1
OutCall.java produces a null pointer exception.

The version 1.1.0 expects at least one listener for incoming calls. If there is no incoming listener (for example OutCall.java) you will receive a null pointer exception.
fixed repaired in version 1.1.1

1.1.0-2
It will be shown an unreadable address of the caller during incoming calls.

This is a bug in the C++ part of the implementation.
fixed repaired in version 1.1.1

1.1.1-1
There is no address of the caller during incoming calls displayed although an address is available.

The address of the caller is privided asynchroniosly by TAPI. The C++ part of the implementation did not consider this.
fixed repaired in version 1.1.2

1.1.1-2
It is not possible to establish a call.

The implementation used per default the media mode INTERACTIVEVOICE. Some of the TAPI driver did not support the establishment of calls in this media mode. The media mode DATAMODEM is the default mode in version 1.1.2.
fixed repaired in version 1.1.2

1.1.2-1 During the read of the saved destination addresses in the option dialog each second line is skiped. fixed repaired in version 1.1.3

1.1.2-2 If there is no listener added for incoming or outgoing calls the first event lead to a NullPointerException. fixed repaired in version 1.1.3

ID	Synopsis	Current State	Last Modified
1.1.0-1	OutCall.java produces a null pointer exception. The version 1.1.0 expects at least one listener for incoming calls. If there is no incoming listener (for example OutCall.java) you will receive a null pointer exception.	fixed	repaired in version 1.1.1
1.1.0-2	It will be shown an unreadable address of the caller during incoming calls. This is a bug in the C++ part of the implementation.	fixed	repaired in version 1.1.1
1.1.1-1	There is no address of the caller during incoming calls displayed although an address is available. The address of the caller is privided asynchroniosly by TAPI. The C++ part of the implementation did not consider this.	fixed	repaired in version 1.1.2
1.1.1-2	It is not possible to establish a call. The implementation used per default the media mode INTERACTIVEVOICE. Some of the TAPI driver did not support the establishment of calls in this media mode. The media mode DATAMODEM is the default mode in version 1.1.2.	fixed	repaired in version 1.1.2
1.1.2-1	During the read of the saved destination addresses in the option dialog each second line is skiped.	fixed	repaired in version 1.1.3
1.1.2-2	If there is no listener added for incoming or outgoing calls the first event lead to a NullPointerException.	fixed	repaired in version 1.1.3

I'm very interested in your opinion of LongJTAPI and LongDialer. The shortest way is the answer form.

© Ralf Lange, longsoft Dresden
Comments & suggestions: webmaster form - Last Modification: 2007-03-01
Java and all Java based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the USA and in other countries. All other mentioned companies and product names are trademarks or registered trademarks of each manufacturer.