Arbortext Programmers’ Guide
Introduction to the Arbortext Object Model (AOM)
The AOM provides object-oriented programming access to Arbortext Editor and Arbortext Publishing Engine. The AOM supports the W3C DOM (Document Object Model) Core and Validation interfaces with extensions, and provides many additional interfaces for Arbortext-specifc features that are not part of the DOM.
The Arbortext extensions to the DOM use a naming convention where A (for Arbortext) is prepended to the DOM interface name; for example, the Arbortext extension for the DOM Node interface is ANode.
The following diagram shows the relationship between Arbortext Editor and Arbortext Publishing Engine, the DOM and AOM interfaces, and programs or scripts accessing the DOM and AOM
Arbortext Publishing Engine Programmers’ Guide
The Arbortext Publishing Engine is implemented as a Java Servlet that complies with the Java Servlet Specifcation, v2.4 from Sun Microsystems. The servlet is called the Arbortext PE Request Manager. This implementation makes the Arbortext Publishing Engine portable across platforms, operating systems, and web servers.It runs in the Tomcat servlet container (which can operate alone or in conjunction with the Microsoft Internet Information Server on Windows and the Apache HTTP Server on Solaris and Linux), and in the servlet containers that are part of the Sun Java System Web Server, BEA WebLogic Server, and IBM WebSphere Application Server.
Arbortext Content Pipeline Programmers’ Guide
Arbortext Editor and the Arbortext Publishing Engine use a SAX filter pipeline,called a composer, to transform documents. A composer is a processor that can be configured to transform a document by passing it through one or more SAX filters in a filter pipeline. The result of this transformation may be one or more XML documents or external files. A content pipeline is defined in a CCF file, and exposed as an AOM composer object.
You can configure and run a composer object using an associative array of parameters. Users can create new composer objects or customize existing ones by subclassing existing filters in a pipeline or by adding or deleting filters in a CCF file to create new pipelines.
A composer is created by calling a createComposer method. When this method is called, the following process occurs:
■ The composer’s CCF file is parsed.
■ For each filter in the pipeline, the composer
□ Creates the adapter from the class specified in the adapterClass attribute.
□ Creates the filter.
□ Links the filter to its predecessor.
□ Maps the interface parameters to the filter’s parameters.