Filter elements

In the previous examples, Bookmarks elements appeared as children of PDF elements, reflecting the fact that bookmarks are one of the content types that can be contained in PDF documents. By contrast, the following example shows a PDF source element as the child of a Bookmarks result element.

Example: Using a bookmarks result element

<Bookmarks result="doc1.xml">

	<PDF source="doc2.pdf"/>

</Bookmarks>

Because the PDF source element is the child of a Bookmarks element, only the bookmarks in doc2.pdf contribute to the result element. Unlike a PDF element, which implicitly contains other types of content, a Bookmarks element can contain only bookmarks. Therefore, doc1.xml is an XML representation of the bookmarks that came from doc2.pdf. (See Exporting and importing bookmarks for more information on bookmarks.)

This example can be extended to have two PDF source elements. Since they are siblings, their content is concatenated and the bookmarks from the combined document constitute the result.

Example: Getting bookmarks from two source documents

<Bookmarks result="doc1.xml">

	<PDF source="doc2.pdf"/>

	<PDF source="doc3.pdf"/>

</Bookmarks>

Note: The bookmarks in doc3.pdf are updated to adjust to their new page locations. For example, if doc2.pdf has five pages, a bookmark in doc3.pdf that refers to page 2 will be updated in the result document to refer to page 7.

In the following example, the result (doc1.xml) is used as a source element to provide content to a PDF result element.

Example: Using a result as a source element in a subsequent step

<Bookmarks result="doc1.xml">

	<PDF source="doc2.pdf"/>

	<PDF source="doc3.pdf"/>

</Bookmarks>

<PDF result="doc4.pdf">

	<PDF source="doc5.pdf"/>

	<Bookmarks source="doc1.xml"/>

</PDF>

This example illustrates an important point: a result element can be used as a source element. The order of result elements matters: if the PDF result block appeared before the Bookmarks result block, an error would occur.

The following example is equivalent, except that only doc4.pdf is returned and no Bookmarks result is generated in the process.

Example: Using a bookmarks filter element

<PDF result="doc4.pdf">

	<PDF source="doc5.pdf"/>

	<Bookmarks>

		<PDF source="doc2.pdf"/>

		<PDF source="doc3.pdf"/>

	</Bookmarks>

</PDF>

In this case, the Bookmarks element is referred to as a filter element. It has neither a source nor a result attribute but is functioning as both types. It contains the result of filtering the bookmarks from doc2.pdf and doc3.pdf and also provides source bookmark content to doc4.pdf.

Note: A filter element, just like a source element of the same type, provides only content of its type. That is, no content from doc2.pdf and doc3.pdf other than bookmarks is included in the assembly.

Current page: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/sdkHelp/assemblePDFDDX_basics.95.8.html