PDF Java Toolkit

Getting Started

Datalogics PDF Java Toolkit is a native Java library that provides high-level APIs for automating PDF workflows like processing PDF forms, verifying digital signatures, and extracting text. It also offers low-level APIs for working directly with the structure of the PDF for those times you need it. As a developer, you can use Datalogics PDF Java Toolkit to build PDF document processing into your own application. While written with Java developers in mind, Datalogics PDF Java Toolkit can be used with any JVM language, such as Clojure or Groovy.

Components of Datalogics PDF Java Toolkit

Datalogics PDF Java Toolkit is made up of multiple components, including PDF Java Toolkit Core and Talkeetna, as well as a set of sample programs.

PDF Java Toolkit Core

PDF Java Toolkit Core offers a variety of features when working with PDF documents, such as:

  1. Create and manage digital signatures in PDF documents
  2. Build and edit PDF forms or import/export data into/from PDF forms
  3. Manage PDF document processing, such as creating and editing PDF files, adding text and graphics, applying watermarks, backgrounds, and headers/footers, deleting pages, and extracting text and graphics

PDF Java Toolkit Core requires Java 7.

Talkeetna

Datalogics built Talkeetna as an API on top of PDF Java Toolkit Core, providing interfaces to easily create PDF documents programmatically. Talkeetna automatically manages the text layout so that you don’t have to think about including line and page breaks to start a new line or page.

Talkeetna requires Java 7 as it takes advantage internally of the try with resources pattern.

RELite

RELite is a command line utility that can be used to reader enable PDF documents so that when a user opens the PDF in Adobe Reader an additional set of features are enabled. For more about RELite, please see Using RELite to reader enable PDFs

Samples

Datalogics provides a set of sample programs with PDF Java Toolkit to demonstrate how to work with the APIs in order to build common PDF workflows. They are included in the PDF Java Toolkit download, appearing in the samples directory, and are also available from a public GitHub repository, PDF Java Toolkit Samples. This GitHub repository allows you to easily access the latest updates to these sample programs, as well as additional samples not included with the package downloaded from Datalogics.

The samples directory includes supporting materials, including the license for the sample programs, Java coding guidelines, and guidelines for contributing samples and source code back to the PDF Java Toolkit Samples project on GitHub.

The PDF Java Toolkit samples are distributed as an Apache Maven project that can be imported easily into IDEs like Eclipse or NetBeans. Refer to the Maven documentation for details on how to use Maven with your IDE.

repo, a Maven repository

When you unzip the product file, there will be a directory named repo. The repo directory is a Maven repository, where the JAR files for PDF Java Toolkit Core and Talkeetna are stored. You can import this directory as a Maven repository into a Maven repository local to your machine if you are comfortable with Maven or simply find the JAR files for PDF Java Toolkit Core and Talkeetna and copy them into your project.

There are a few other JAR files contained in the Maven repository in the repo directory that might be useful to you as well. The pdf-java-toolkit-samples-lite.jar provides pre-built versions of the sample programs that ship with Datalogics PDF Java Toolkit, allowing them to be run without having to compile them first. For PDF Java Toolkit Core and Talkeetna, there are additional JAR files that contain the Javadoc for each that can be imported into IDEs that support browsing Javadoc.

Documentation

The docs directory contains the Javadoc for all of the components of Datalogics PDF Java Toolkit, which collectively serve as a programming reference. In the docs directory, you will also find the current release notes, a copy of the End User License Agreement (EULA), and acknowledgments for several third-party libraries.

You can start browsing the documentation by opening the index.html file found in the root of the docs directory.