generated from camel.apache.org/component
Update wiki Home page for fop
parent
bdaa5f054c
commit
76fa065981
38
Home.md
38
Home.md
@ -1,21 +1,31 @@
|
|||||||
# Deploy the Project on CamelX Platform
|
# FOP
|
||||||
|
|
||||||
Deploy on CamelX Platform in three steps
|
Render messages into PDF and other output formats supported by Apache FOP.
|
||||||
|
|
||||||
## Step 1: Create a release
|
## Metadata
|
||||||
From the project space, click on **"Create a release"**
|
|
||||||
|
|
||||||
The new version is automatically available in the list
|
| Property | Value |
|
||||||
|
|----------|-------|
|
||||||
|
| Scheme | `fop` |
|
||||||
|
| Support Level | Stable |
|
||||||
|
| Labels | file,transformation |
|
||||||
|
| Version | 4.10.2 |
|
||||||
|
|
||||||
## Step 2: Deploy
|
## Maven Dependency
|
||||||
Click on **"Deploy"**
|
|
||||||
|
|
||||||
- **Version:** Select the desired release
|
```xml
|
||||||
- **Environment:** Choose `Development`, `Staging`, or `Production`
|
<dependency>
|
||||||
- **Configuration:** Select the configuration source
|
<groupId>org.apache.camel</groupId>
|
||||||
- **Resources:** Set CPU and Memory
|
<artifactId>camel-fop</artifactId>
|
||||||
|
<version>4.10.2</version>
|
||||||
|
</dependency>
|
||||||
|
```
|
||||||
|
|
||||||
## Step 3: Expose
|
## Endpoint Properties
|
||||||
Enable **"Expose"**
|
|
||||||
|
|
||||||
Choose an **API Gateway** (Internal, Public, etc.)
|
| Name | Type | Required | Default | Description |
|
||||||
|
|------|------|----------|---------|-------------|
|
||||||
|
| `outputType` | object | ✓ | | The primary output format is PDF but other output formats are also supported. |
|
||||||
|
| `fopFactory` | object | | | Allows to use a custom configured or implementation of org.apache.fop.apps.FopFactory. |
|
||||||
|
| `userConfigURL` | string | | | The location of a configuration file which can be loaded from classpath or file system. |
|
||||||
|
| `lazyStartProducer` | boolean | | `false` | 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. |
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user