The Output service renders a non-interactive PDF form that
is based on a form design that is typically saved as an XDP file
and created in Designer. As of LiveCycle ES2.5, you can pass a com.adobe.idp.Document object
that contains the form design to the Output service. The Output
service then renders the form design located in the com.adobe.idp.Document object.
An advantage of passing a com.adobe.idp.Document object
to the Output service is that other LiveCycle service operations
return a com.adobe.idp.Document instance. That
is, you can get a com.adobe.idp.Document instance
from another service operation and render it. For example, assume
that an XDP file is stored in the LiveCycle repository,
as shown in the following illustration.
The FormsFolder folder is a user-defined location in the
LiveCycle repository (this location is an example and does
not exist by default). In this example, a form design named Loan.xdp
is located in this folder. In addition to the form design, other
form collateral such as images can be stored in this location. The
path to a resource located in the LiveCycle repository is:
You can programmatically retrieve Loan.xdp from the LiveCycle repository and pass it to the Output service within a com.adobe.idp.Document object.
You can create a PDF based on an XDP file located in the repository
using one of two ways. You can pass the XDP loction by reference
or you can programmatically retrieve the XDP from the repository
and pass it to the Output service within an XDP file.
Quick Start (EJB mode): Creating a PDF document based on an application XDP file using the Java API (shows how to pass the location
of the XDP file by reference).
Quick Start (EJB mode): Passing a document located in the LiveCycle Repository to the Output service using the Java API (shows
how to programmatically retrieve the XDP file from the LiveCycle Repository and pass it to the Output service within a com.adobe.idp.Document instance).
(This section discusses how to perform this task)