이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 105. FOP Component
Available as of Camel version 2.10
The FOP component allows you to render a message into different output formats using Apache FOP.
Maven users will need to add the following dependency to their pom.xml
for this component:
105.1. URI format 링크 복사링크가 클립보드에 복사되었습니다!
fop://outputFormat?[options]
fop://outputFormat?[options]
105.2. Output Formats 링크 복사링크가 클립보드에 복사되었습니다!
The primary output format is PDF but other output formats are also supported:
name | outputFormat | description |
---|---|---|
| application/pdf | Portable Document Format |
PS | application/postscript | Adobe Postscript |
PCL | application/x-pcl | Printer Control Language |
PNG | image/png | PNG images |
JPEG | image/jpeg | JPEG images |
SVG | image/svg+xml | Scalable Vector Graphics |
XML | application/X-fop-areatree | Area tree representation |
MIF | application/mif | FrameMaker’s MIF |
RTF | application/rtf | Rich Text Format |
TXT | text/plain | Text |
The complete list of valid output formats can be found here
105.3. Endpoint Options 링크 복사링크가 클립보드에 복사되었습니다!
The FOP component has no options.
The FOP endpoint is configured using URI syntax:
fop:outputType
fop:outputType
with the following path and query parameters:
105.3.1. Path Parameters (1 parameters): 링크 복사링크가 클립보드에 복사되었습니다!
Name | Description | Default | Type |
---|---|---|---|
outputType | Required The primary output format is PDF but other output formats are also supported. | FopOutputType |
105.3.2. Query Parameters (3 parameters): 링크 복사링크가 클립보드에 복사되었습니다!
Name | Description | Default | Type |
---|---|---|---|
fopFactory (producer) | Allows to use a custom configured or implementation of org.apache.fop.apps.FopFactory. | FopFactory | |
userConfigURL (producer) | The location of a configuration file which can be loaded from classpath or file system. | String | |
synchronous (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean |
The location of a configuration file with the following structure. From Camel 2.12 onwards the file is loaded from the classpath by default. You can use file:
, or classpath:
as prefix to load the resource from file or classpath. In previous releases the file is always loaded from file system.
fopFactory
Allows to use a custom configured or implementation of org.apache.fop.apps.FopFactory
.
105.4. Message Operations 링크 복사링크가 클립보드에 복사되었습니다!
name | default value | description |
---|---|---|
CamelFop.Output.Format | Overrides the output format for that message | |
CamelFop.Encrypt.userPassword | PDF user password | |
CamelFop.Encrypt.ownerPassword | PDF owner passoword | |
CamelFop.Encrypt.allowPrint | true | Allows printing the PDF |
CamelFop.Encrypt.allowCopyContent | true | Allows copying content of the PDF |
CamelFop.Encrypt.allowEditContent | true | Allows editing content of the PDF |
CamelFop.Encrypt.allowEditAnnotations | true | Allows editing annotation of the PDF |
CamelFop.Render.producer | Apache FOP | Metadata element for the system/software that produces the document |
CamelFop.Render.creator | Metadata element for the user that created the document | |
CamelFop.Render.creationDate | Creation Date | |
CamelFop.Render.author | Author of the content of the document | |
CamelFop.Render.title | Title of the document | |
CamelFop.Render.subject | Subject of the document | |
CamelFop.Render.keywords | Set of keywords applicable to this document |
105.5. Example 링크 복사링크가 클립보드에 복사되었습니다!
Below is an example route that renders PDFs from xml data and xslt template and saves the PDF files in target folder:
from("file:source/data/xml") .to("xslt:xslt/template.xsl") .to("fop:application/pdf") .to("file:target/data");
from("file:source/data/xml")
.to("xslt:xslt/template.xsl")
.to("fop:application/pdf")
.to("file:target/data");
For more information, see these resources…
105.6. See Also 링크 복사링크가 클립보드에 복사되었습니다!
- Configuring Camel
- Component
- Endpoint
- Getting Started