Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.Questo contenuto non è disponibile nella lingua selezionata.
8.7. Manifest
8.7.1. Manifest Copia collegamentoCollegamento copiato negli appunti!
Copia collegamentoCollegamento copiato negli appunti!
The Manifest is where you specify from where the "intelligence" of the component is to come. For the BPM component, you need to specify, at the minimum, the location of the BPMN 2 process definition file. For the Rules component, you can specify the location of DRL, DSL, DSLR or XLS files.
8.7.2. Ways of Configuring the Manifest Copia collegamentoCollegamento copiato negli appunti!
Copia collegamentoCollegamento copiato negli appunti!
Note
The following code examples assume there is a DRL file located on the classpath at
com/example/MyRules.drl
.
There are two ways to to configure the Manifest:
- with a KIE Container. (This relies upon the existence of a
META-INF/kmodule.xml
configuration file.)Here is the sampleMETA-INF/kmodule.xml
file:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Here is the sample XML file:<manifest> <container sessionName="my-session"/> </manifest>
<manifest> <container sessionName="my-session"/> </manifest>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow In addition to the sessionName attribute, you can also specify baseName and releaseId, if you desire.To enable it to scan for updates, simply setscan="true"
and, optionally,scanInterval=<# of milliseconds>
scanInterval=<# of milliseconds>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - with a manually defined list of resources.Here is the sample XML file:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Important
These two options are mutually exclusive: You have to choose one or the other.