Since Camel 2.16
Only producer is supported
The PDF components provides the ability to create, modify or extract content from PDF documents. This component uses Apache PDFBox as underlying library to work with PDF documents.
In order to use the PDF component, Maven users will need to add the
following dependency to their pom.xml:
pom.xml
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-pdf</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>Options
The PDF component supports 2 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
basicPropertyBinding (advanced) |
Deprecated Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
boolean |
The PDF endpoint is configured using URI syntax:
pdf:operation
with the following path and query parameters:
Path Parameters (1 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
operation |
Required Operation type. There are 3 enums and the value can be one of: create, append, extractText |
PdfOperation |
Query Parameters (11 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
font (producer) |
Font. There are 14 enums and the value can be one of: Courier, Courier-Bold, Courier-Oblique, Courier-BoldOblique, Helvetica, Helvetica-Bold, Helvetica-Oblique, Helvetica-BoldOblique, Times-Roman, Times-Bold, Times-Italic, Times-BoldItalic, Symbol, ZapfDingbats |
Helvetica |
String |
fontSize (producer) |
Font size in pixels |
14.0 |
float |
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
marginBottom (producer) |
Margin bottom in pixels |
20 |
int |
marginLeft (producer) |
Margin left in pixels |
20 |
int |
marginRight (producer) |
Margin right in pixels |
40 |
int |
marginTop (producer) |
Margin top in pixels |
20 |
int |
pageSize (producer) |
Page size. There are 9 enums and the value can be one of: LETTER, LEGAL, A0, A1, A2, A3, A4, A5, A6 |
A4 |
String |
textProcessingFactory (producer) |
Text processing to use. autoFormatting: Text is getting sliced by words, then max amount of words that fits in the line will be written into pdf document. With this strategy all words that doesn’t fit in the line will be moved to the new line. lineTermination: Builds set of classes for line-termination writing strategy. Text getting sliced by line termination symbol and then it will be written regardless it fits in the line or not. There are 2 enums and the value can be one of: autoFormatting, lineTermination |
lineTermination |
TextProcessingFactory |
basicPropertyBinding (advanced) |
Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
boolean |
synchronous (advanced) |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
boolean |
Headers
| Header | Description |
|---|---|
|
Mandatory header for |
|
Expected type is ProtectionPolicy. If specified then PDF document will be encrypted with it. |
|
Expected type is DecryptionMaterial. Mandatory header if PDF document is encrypted. |
Spring Boot Auto-Configuration
When using pdf with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-pdf-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>The component supports 3 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
camel.component.pdf.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.pdf.enabled |
Whether to enable auto configuration of the pdf component. This is enabled by default. |
Boolean |
|
camel.component.pdf.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |