- Adapt the implementation to the specification of JTAPI 1.4.
- All classes and methods of the implementation of the observer pattern are
marked as deprecated.
- This implementation works only with Java version 1.4.x and above.
- Support for TAPI version 2.2 in the native part.
- Fix the Bug 1.1.3-1. (see bug parade)
- Complete implementation of the JTAPI Core Package. New is the answer method
of the TerminalConnection class and the handling of ProviderEvents in the
Call and the TerminalConnection class. Now it is possible to handle incoming
- A configuration dialog is provided to select the TAPI lines and the addresses
of the providers domain.
- The implementation of the Address is splitted in a LocalAddress and a RemoteAddress.
The LocalAddresses are the addresses of the provider domain and be managed
by the Provider. The RemoteAddresses are only provided as a objecte and not
managed. In that way it is possible to establish a connection to all desitination
- All capabilities are located in a separate package.
- All classes necessary for the observer pattern are removed.
- The Provider provided a new implementation of the shutdown method. These
method cancel all existing connections and release all allocated memory.
- All configuration informations are saved in a file with the name "LongJTAPI.config".
These file is readed at the next using of LongJTAPI. These file replace the
- Ant build files exists for all parts of LongJTAPI to create the JAR files
and the documentation verry easy.
- The complete native part is new implemented.
- Controls the complete call from the beginning to the end.
- All configuration informations are saved in a file with the name "LongDialer.config".
These file is readed at the next using of LongDialer.
- A local address can only be selected from the addresses of the provider
- An Ant build file exists for LongDialer to create the JAR file and the documentation
- The first public version.
- One outgoing call can be set up. The application loses control over the
call after finishing the set up.
- There is no reaction on incomming calls.
- All wanted addresses must be declared in the properties, before the provider
can be started.
- The used TAPI line is selected automatically.
- The initialisation of the provider starts when the outgoing call is set
up and finishes immediately after the asynchronius end of the TAPI call.
- Information like memo names and addresses are not saved.
- The provider is not destructed correctly (no shutdown() call).
© 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