The Assembler service's dynamic assembly capabilities allow for XDP files to be joined and for fragments to be placed at insertion points in XDP files. If form designers use the LiveCycle Designer ES2 default behavior of relatively referencing fragments and images, other LiveCycle ES2 services sometimes have trouble assembling and rendering the form. In particular, these problems can occur:
These limitations will be resolved in a future service pack.
LiveCycle ES2 Designer and the Assembler service let you create XML form templates that include fragments. A fragment is a part of a form that is used in other forms. Using fragments simplifies and speeds up the creation and maintenance of large numbers of forms.
Here is an illustration that shows how fragments and images can be used in a base form. The base form references two fragments. One of those fragments references an image. The lower form shows the appearance of the assembled and rendered form.
Form designers can insert fragments into a form by selecting a fragment from a fragment library. In the XML version of the form, Designer inserts corresponding references to the fragments. By default, these references are relative.
Subforms from an existing form can be extracted as a fragment into the fragment library. In this case, the form designer can replace the subform with a reference to the extracted fragment (which is the default behavior) or keep the subform content as it is.
When form designers add image objects to a form, they can specify a URL or browse to the location of the image. In the latter case, Designer by default uses a relative reference to identify the location of the image file.
When the Forms or Output service renders an XDP form, it cannot resolve relative image references (for example ../myImage.jpg) that appear within fragments that are used to construct the form. With XDP forms that have such unresolved images, these services render the XDP form, but the result omits unresolved images. They also provide a warning indicating that images cannot be resolved.
Form designers can ensure the Forms or Output service can resolve image references by embedding the image in the form or changing the image reference to an absolute URL that correctly locates the image. Here is an example of an absolute URL: File:///myDirectory/myImage.jpg. The Designer ES2 default behavior is to use relative references for images.
With XDP dynamic assembly, developers create DDX documents that direct the Assembler service to import fragments into insertion points within an XML form template. Those DDX documents can also import fragments into the insertion points of another fragment. The DDX expressions cannot specify images to import into a form or fragment. Instead, form designers create image references.
When the Assembler service processes a DDX document that specifies an XDP source as a document object (via the input map) or as a File URL, it cannot resolve relative references to fragments that appear within that XDP source. Also, it cannot resolve relative references to fragments that appear within other fragments that are included in the XDP source (nested fragments). Here is an example of a relative reference ../myForm.xdp.
In contrast, if the DDX document uses an application or repository URL to specify the XDP source, and if the XDP form and fragments also use application or repository URLs, then the Assembler service can resolve relative and absolute references to fragments.
When the Assembler service is unable to resolve references to fragments, it terminates the job with this error:
The operation-name operation failed on XDP name.
XFA Dynamic assembler failed to stitch a fragment.
There are two ways to avoid this problem: