|
|
In the following example, two packages are assembled. The new package specification is created by aggregating the two package specifications. If any PDF source is a package, the resulting document will be a package. If none of the PDF sources are packages, the result is a single PDF. To force the result to be a package, without overriding any package specifications, add <Package/> within the <PDF> result block.Example: Assembling packages<PDF result="newPackage"><PDF source="pkg2"/><PDF source="pkg3"/></PDF>In the following example, the explicit Package element specifies only the package specification that exists in pkg1. As the package specification is explicitly specified, it does not include the specifications from pkg2 or pkg3. However, the package files only come from pkg2 and pkg3, and not pkg1. No cover sheet is specified, so the default cover sheet (the_AdobeCoverSheet) is provided.<PDF result="newPackage"><Package><PDF source="pkg1"/></Package><PDF source="pkg2"/><PDF source="pkg3"/></PDF>In the example above, if pkg1 was only a single PDF, it would contribute nothing to the assembly, and the package specification would start with pkg2 followed by the specification contained in pkg3. In this case, the DDX could appear as shown in the example below:<PDF result="newPackage"><Package /><PDF source="pkg2"/><PDF source="pkg3"/></PDF>As shown in the example below, if you would like to specify a new display order for the metadata but retain the same schema and sort order already contained in pkg1, specify only a DisplayOrder element within the Package element.<PDF result="newPackage"><Package><DisplayOrder><Field name="Phone" /><Field name="Last Name" /><Field name="First Name" /><Field name="Address" /></DisplayOrder></Package><PDF source="pkg1"/></PDF>
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/sdkHelp/assemblePDFAssembling.96.12.html