AOM Packages

Arbortext Editor and the Arbortext Publishing Engine ship with Java classes for using the AOM from the Java programming language. The supplied Java classes are stored in a Java archive file Arbortext-path\lib\classes\aom.jar and are intended for developer use. The AOM and DOM Java classes and interfaces are stored in the following packages:

Package	Description
com.arbortext.epic	The core interfaces of the AOM, including the singleton Application and Acl objects.
com.arbortext.epic.table	The table-related interfaces for the AOM, including the TableObject superinterface.
com.arbortext.epic.ui	User interface-related interfaces for the AOM, including the Component superinterface.
org.w3c.dom	The core interfaces for the W3C Document Object Model (DOM).
org.w3c.dom.events	The interfaces for the W3C DOM Events specification.
org.w3c.dom.ranges	The interfaces for the W3C DOM Ranges specification.
org.w3c.dom.views	The interfaces for the W3C DOM Views specification.

All the methods in the Application class and the Acl class are class methods. Therefore you will never need an instance of the Application or an Acl object.

If you inspect the aom.jar file, you will find additional packages (for example, com.arbortext.epic.internal). These additional packages are for Arbortext internal use and should not be used in your Java programs.

Your Java program should import the required AOM and DOM packages. For example, if you are writing a DOM event handler you would need to import at least the following packages:

The com.arbortext.epic.ui package defines several AOM-specific interfaces that have the same names as some in the java.awt package. If you import the AOM user interface package in a .java source file, do not also import java.awt.