Introduction to Jadt, part 2nd

Use the Java dictionary and Thesaurus APIs to make your word reference available to Java users

In part 1th of this series, you learned some of the basics of JADT, JADT provides a transparent Java-centric way to access dictionaries or unstructured words and their related information. The main goal of JADT is to provide a standard technology for dictionary providers to support the Java platform. The 1th part introduces JADT from the perspective of the developer. In this article, I want to give the details of implementation, focusing on the perspective of the dictionary developer. I will take you through the details of the architecture of JADT and JADT, and provide information about all the classes and interfaces contained in JADT.

With the help of the JADT sample driver implementation, I'll discuss the required interface implementations for the driver. After that, you will have an overall impression of the JADT driver and the method that provides the driver.

JADT Architecture

The JADT architecture provides driver-based access to any type of back-end data. The dictionary provider implements the driver-side interface, provides an access point for the dictionary, and any program using the dictionary will use the Dictionary service's client interface. As a result, you can easily integrate the JADT architecture with a variety of developers and third-party drivers.

Driver implementation and JADT remain separate:

The role of JADT developers

If you want to use JADT to expose your dictionary or thesaurus, simply provide a JADT implementation. The JADT driver is located between developer data and Java programmers, allowing developers to provide services externally without fully disclosing their data and data formats. Turn. Java programmers can use the developer's data without going into the data and data format specific to a developer.

JADT driver developers can use the JADT interface and implement these interfaces according to their own custom. Once the driver is ready to access your data, you can enable it at your site. Links to this site can be used as a thread in the JADT access page.

It is important for JADT to work in all data dictionaries in a consistent way, so it is the developer's responsibility to implement all JADT interfaces and methods that meet the standards set by JADT. JADT's JADT Javadocs and interface definition documents clearly expose the objectives of interfaces and methods.

JADT realize near View

JADT defines multiple sets of interfaces and classes. Some interfaces are accessible, and some are optional, depending on the functionality your driver is supporting. If you want to fully support JADT, you must implement all interfaces according to the specifications defined in Javadocs. In this section, I'll give you all the details of these interfaces and class implementations.

The complete JADT interface and class set, as shown in the class diagram in Figure 2:

Figure 2. JADT class Diagram