mel.camel-spring.2.15.0.source-code.camel-spring.xsd Maven / Gradle / Ivy
Aggregates many messages into a single message
Does processing before and/or after the route is completed
Avro data format
Barcode data format
Base64 data format
Configures batch-processing resequence eip.
Calls a java bean
BeanIO data format
Bindy data format
Castor data format
Routes messages based on a series of predicates
Circuit break load balancer
For expressions and predicates using a constant
Scans for Java org.apache.camel.builder.RouteBuilder instances in the context org.apache.camel.spi.Registry.
Converts the message body to another type
Crypto data format
CSV data format
Custom data format
Custom load balancer
To configure data formats
Delays processing for a specified length of time
Rest DELETE command
To provide comments about the node.
Catches exceptions as part of a try catch finally block
Path traversed when a try catch finally block exits
Marks the beginning of a try catch finally block
Routes messages based on dynamic rules
For EL expressions and predicates
Enriches a message with data from a secondary resource
An expression which extracts the named exchange property
A useful base class for an expression
Failover load balancer
Filter out messages based using a predicate
Flatpack data format
Act as a message source as input to a route
Rest GET command
For Groovy expressions and predicates
GZip data format
Rest HEAD command
An expression which extracts the named exchange header
HL7 data format
iCal data format
Filters out duplicate messages
Marks the exchange pattern for the route to one way
Marks the exchange pattern for the route to request/reply
Intercepts a message at each step in the route
Intercepts incoming messages
Intercepts messages being sent to an endpoint
For JavaScript expressions and predicates
JAXB data format
JiBX data format
Json data format
For JSonPath expressions and predicates
For JXPath expressions and predicates
Represents a parameterised language expression which can support any language at runtime using the language attribute.
Balances message processing among a number of nodes
Logs the defined message to the logger
Processes a message multiple times
Marshals data into a specified format for transmission over a transport or component
For expressions and predicates using a java bean (aka method call)
Routes the same message to multiple paths either sequentially or in parallel.
For MVEL expressions and predicates
For OGNL expressions and predicates
Route to be executed when normal route processing completes
Route to be executed when an exception is thrown
To configure optimistic locking
Route to be executed when all other choices evaluate to false
Scans for Java org.apache.camel.builder.RouteBuilder classes in java packages
PGP data format
For PHP expressions and predicates
Routes the message to a sequence of processors.
Defines a policy the route will use
Enriches messages with data polled from a secondary resource
Rest POST command
Calls a Camel processor.
A series of key value pair
A key value pair
Google protobuf data format
Rest PUT command
For Python expressions and predicates
Random load balancer
Routes messages to a number of dynamically specified recipients (dynamic to)
To configure re-delivery for error handling
For using a custom expression
Removes a named header from the message
Removes message headers whose name matches a specified pattern
Removes message exchange properties whose name matches a specified pattern
Removes a named property from the message exchange
Resequences (re-order) messages based on an expression
Defines a rest service using the rest-dsl
To configure rest binding
To configure rest
To refer to an XML file with rest services defined using the rest-dsl
A key value pair
A series of rest services defined using the rest-dsl
Forces a rollback by stopping routing the message
Round robin load balancer
A Camel route
To refer to a Java org.apache.camel.builder.RouteBuilder instance to use.
To refer to an XML file with routes defined using the xml-dsl
A series of Camel routes
Routes a message through a series of steps that are pre-determined (the slip)
RSS data format
For Ruby expressions and predicates
Extract a sample of the messages passing through a route
xml-security data format
Java Object Serialization data format
Sets the contents of the message body
Sets the exchange pattern on the message exchange
Sets the contents of a fault message's body
Sets the value of a message header
Sets the value of a header on the outbound message
Sets a named property on the message exchange
For expressions and predicates using the simple language
SOAP data format
Sorts the contents of the message
For Spring Expression Language (SpEL) expressions and predicates
Splits a single message into many sub-messages.
For SQL expressions and predicates
Sticky load balancer
Stops the processing of the current message
Configures stream-processing resequence eip.
Represents the String (text based) DataFormat
Syslog data format
For HL7 terser expressions and predicates
To configure thread pools
Specifies that all steps after this node are processed asynchronously
Controls the rate at which messages are passed to the next node in the route
Throws an exception
Tidymark (wellformed HTML) data format
Sends the message to an endpoint
For expressions and predicates using a body or header tokenizer.
Topic load balancer
Enables transaction on the route
Transforms the message body based on an expression
UniVocity CSV data format
UniVocity fixed-width data format
To configure headers for UniVocity data formats.
UniVocity TSV data format
Converts the message data received from the wire into a format that Apache Camel processors can consume
Validates a message based on an expression
Rest command
For VTD-XML (fast and efficient XPath) expressions and predicates
Weighted load balancer
Triggers a route when an expression evaluates to true
Predicate to determine if the message should be sent or not to the endpoint when using interceptSentToEndpoint.
Routes a copy of a message (or creates a new message) to a secondary destination while continue routing the original message.
XMLBeans data format
xml-json data format
xml-rpc data format
For XPath expressions and predicates
For XQuery expressions and predicates
xstream data format
For expressions and predicates using a body or header tokenizer.
zip data format (not for zip files)
zip-file data format
Sets the value of the id property.
Property key
Property value
Endpoint to call in AOP before.
Endpoint to call in AOP after. The difference between after and afterFinally is that afterFinally is invoked from a finally block so it will always be invoked no matter what eg also in case of an exception occur.
Endpoint to call in AOP after finally. The difference between after and afterFinally is that afterFinally is invoked from a finally block so it will always be invoked no matter what eg also in case of an exception occur.
Sets whether or not to inherit the configured error handler. The default value is true. You can use this to disable using the inherited error handler for a given DSL such as a load balancer where you want to use a custom error handler strategy.
Sets the id of this node
Language such as en for english.
Layout position X
Layout position Y
Layout width
Layout height
When aggregated are completed they are being send out of the aggregator. This option indicates whether or not Camel should use a thread pool with multiple threads for concurrency. If no custom thread pool has been specified then Camel creates a default pool with 10 concurrent threads.
Turns on using optimistic locking which requires the aggregationRepository being used is supporting this by implementing org.apache.camel.spi.OptimisticLockingAggregationRepository.
If using parallelProcessing you can specify a custom thread pool to be used. In fact also if you are not using parallelProcessing this custom thread pool is used to send out aggregated exchanges as well.
If using either of the completionTimeout completionTimeoutExpression or completionInterval options a background thread is created to check for the completion for every aggregator. Set this option to provide a custom thread pool to be used rather than creating a new thread for every aggregator.
Sets the custom aggregate repository to use Will by default use org.apache.camel.processor.aggregate.MemoryAggregationRepository
A reference to lookup the AggregationStrategy in the Registry. Configuring an AggregationStrategy is required and is used to merge the incoming Exchange with the existing already merged exchanges. At first call the oldExchange parameter is null. On subsequent invocations the oldExchange contains the merged exchanges and newExchange is of course the new incoming Exchange.
This option can be used to explicit declare the method name to use when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used for the very first aggregation. If this option is true then null values is used as the oldExchange (at the very first aggregation) when using POJOs as the AggregationStrategy.
Sets the completion size which is the number of aggregated exchanges which would cause the aggregate to consider the group as complete and send out the aggregated exchange.
Sets the completion interval which would cause the aggregate to consider the group as complete and send out the aggregated exchange.
Sets the completion timeout which would cause the aggregate to consider the group as complete and send out the aggregated exchange.
Enables the batch completion mode where we aggregate from a org.apache.camel.BatchConsumer and aggregate the total number of exchanges the org.apache.camel.BatchConsumer has reported as total by checking the exchange property link org.apache.camel.ExchangeBATCH_COMPLETE when its complete.
Enables grouped exchanges so the aggregator will group all aggregated exchanges into a single combined Exchange holding all the aggregated exchanges in a java.util.List.
Use eager completion checking which means that the completionPredicate will use the incoming Exchange. At opposed to without eager completion checking the completionPredicate will use the aggregated Exchange.
If a correlation key cannot be successfully evaluated it will be ignored by logging a DEBUG and then just ignore the incoming Exchange.
Closes a correlation key when its complete. Any late received exchanges which has a correlation key that has been closed it will be defined and a org.apache.camel.processor.aggregate.ClosedCorrelationKeyException is thrown.
Discards the aggregated message on completion timeout. This means on timeout the aggregated message is dropped and not sent out of the aggregator.
Indicates to complete all current aggregated exchanges when the context is stopped
Sets the id of this node
Whether to trim the value to remove leading and trailing whitespaces and line breaks
Sets the maximum number of retries
Sets the delay in millis between retries
Sets the upper value of retry in millis between retries when using exponential or random backoff
Enable exponential backoff
Enables random backoff
Sets a reference to a bean to use
Sets the method name on the bean to use
Sets the Class of the bean
Caches the bean lookup to avoid lookup up bean on every usage.
Whether the message body is an array type.
The java type to convert to
To use a specific charset when converting
Refers to a custom Thread Pool if asyncDelay has been enabled.
Enables asynchronous delay which means the thread will noy block while delaying.
Whether or not the caller should run the task when it was rejected by the thread pool. Is by default true
Sets the uri delimiter to use
Ignore the invalidate endpoint exception when try to create a producer with that endpoint
The endpoint uri for the external service to enrich from. You must use either uri or ref.
Refers to the endpoint for the external service to enrich from. You must use either uri or ref.
Refers to an AggregationStrategy to be used to merge the reply from the external service into a single outgoing message. By default Camel will use the reply from the external service as outgoing message.
This option can be used to explicit declare the method name to use when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used if there was no data to enrich. If this option is true then null values is used as the oldExchange (when no data to enrich) when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used if there was an exception thrown while trying to retrieve the data to enrich from the resource. Setting this option to true allows end users to control what to do if there was an exception in the aggregate method. For example to suppress the exception or set a custom message body etc.
Sets the URI of the endpoint to use
Sets the name of the endpoint within the registry (such as the Spring ApplicationContext or JNDI) to use
Sets the reference name of the message id repository
Sets whether to eagerly add the key to the idempotent repository or wait until the exchange is complete. Eager is default enabled.
Sets whether to skip duplicates or not. The default behavior is to skip duplicates. A duplicate message would have the Exchange property link org.apache.camel.ExchangeDUPLICATE_MESSAGE set to a link BooleanTRUE value. A none duplicate message will not have this property set.
Sets whether to remove or keep the key on failure. The default behavior is to remove the key on failure.
Sets the uri of the endpoint to send to.
Sets the reference of the endpoint to send to.
Intercept incoming messages from the uri or uri pattern. If this option is not configured then all incoming messages is intercepted.
Intercept sending to the uri or uri pattern.
If set to true then the message is not sent to the original endpoint. By default (false) the message is both intercepted and then sent to the original endpoint.
To use a custom load balancer. This option is deprecated use the custom load balancer type instead.
Whether or not the failover load balancer should operate in round robin mode or not. If not then it will always start from the first endpoint when a new message is to be processed. In other words it restart from the top for every message. If round robin is enabled then it keeps state and will continue with the next endpoint in a round robin fashion. When using round robin it will not stick to last known good endpoint it will always pick the next endpoint to use.
A value to indicate after X failover attempts we should exhaust (give up). Use -1 to indicate never give up and continuously try to failover. Use 0 to never failover. And use e.g. 3 to failover at most 3 times before giving up. his option can be used whether or not roundRobin is enabled or not.
Refers to the custom load balancer to lookup from the registry
To enable round robin mode. By default the weighted distribution mode is used. The default value is false.
The distribution ratio is a delimited String consisting on integer weights separated by delimiters for example 235. The distributionRatio must match the number of endpoints and/or processors specified in the load balancer list.
Delimiter used to specify the distribution ratio. The default value is
The timeout in millis to use as threshold to move state from closed to half-open or open state
Number of previous failed messages to use as threshold to move state from closed to half-open or open state
Sets the log message (uses simple language)
Sets the logging level. The default value is INFO
Sets the name of the logger
To use slf4j marker
To refer to a custom logger instance to lookup from the registry.
If the copy attribute is true a copy of the input Exchange is used for each iteration. That means each iteration will start from a copy of the same message. By default loop will loop the same exchange all over so each iteration may have different message content.
To refer to a custom data format to use as marshaller
Class name to use for marshal and unmarshalling
To specific a maximum line length for the encoded data. By default 76 is used.
The line separators to use. By default \r\n is used.
Instead of emitting '' and '/' we emit '-' and '_' respectively. urlSafe is only applied to encode operations. Decoding seamlessly handles both modes. Is by default false.
The BeanIO mapping file. Is by default loaded from the classpath. You can prefix with file: http: or classpath: to denote from where to load the mapping file.
The name of the stream to use.
Whether to ignore unidentified records.
Whether to ignore unexpected records.
Whether to ignore invalid records.
The charset to use. Is by default the JVM platform default charset.
Whether to use csv fixed or key value pairs mode.
The java package names to scan for model classes.
Name of model class to use.
To configure a default locale to use such as us for united states. To use the JVM platform default locale then use the name default
Path to a Castor mapping file to load from the classpath.
Whether validation is turned on or off. Is by default true.
Encoding to use when marshalling an Object to XML. Is by default UTF-8
Add additional packages to Castor XmlContext
Add additional class names to Castor XmlContext
The JCE algorithm name indicating the cryptographic algorithm that will be used. Is by default DES/CBC/PKCS5Padding.
The name of the JCE Security Provider that should be used.
Refers to the secret key to lookup from the register to use.
Refers to a byte array containing the Initialization Vector that will be used to initialize the Cipher.
A JCE AlgorithmParameterSpec used to initialize the Cipher. Will lookup the type using the given name as a java.security.spec.AlgorithmParameterSpec type.
The size of the buffer used in the signature process.
The JCE algorithm name indicating the Message Authentication algorithm.
Flag indicating that a Message Authentication Code should be calculated and appended to the encrypted data.
Flag indicating that the configured IV should be inlined into the encrypted data stream. Is by default false.
The reference format to use it will be updated with the other format options the default value is CSVFormat.DEFAULT
The name of the format to use the default value is CSVFormat.DEFAULT
Disables the comment marker of the reference format.
Sets the comment marker of the reference format.
Sets the delimiter to use. The default value is (comma)
Use for disabling using escape character
Sets the escape character to use
Use for disabling headers
Whether to allow missing column names.
Whether to ignore empty lines.
Whether to ignore surrounding spaces
Used to disable null strings
Sets the null string
Used to disable quotes
Sets the quote which by default is
Used for disabling record separator
Sets the record separator (aka new line) which by default is \r\n (CRLF)
Whether to skip the header record in the output
Whether the unmarshalling should produce an iterator that reads the lines on the fly or if all the lines must be read at one.
Whether the unmarshalling should produce maps for the lines values instead of lists. It requires to have header (either defined or collected).
Refers to a custom CsvRecordConverter to lookup from the registry to use.
Reference to the custom org.apache.camel.spi.DataFormat to lookup from the Camel registry.
References to a custom parser factory to lookup in the registry
The flatpack pzmap configuration file. Can be omitted in simpler situations but its preferred to use the pzmap.
Delimited or fixed. Is by default false = delimited
Whether the first line is ignored for delimited files (for the column headers). Is by default true.
If the text is qualified with a char such as "
The delimiter char (could be ; or similar)
Allows for lines to be shorter than expected and ignores the extra characters
Allows for lines to be longer than expected and ignores the extra characters.
Whether to validate the HL7 message Is by default true.
Whether to validate.
Package name where your JAXB classes are located.
To validate against an existing schema. Your can use the prefix classpath: file: or http: to specify how the resource should by resolved. You can separate multiple schema files by using the '' character.
To enable pretty printing output nicely formatted. Is by default false.
Whether to ignore JAXBElement elements - only needed to be set to false in very special use-cases.
Whether marhsalling must be java objects with JAXB annotations. And if not then it fails. This option can be set to false to relax that such as when the data is already in XML format.
To ignore non xml characheters and replace them with an empty space.
To overrule and use a specific encoding
To turn on marshalling XML fragment trees. By default JAXB looks for XmlRootElement annotation on given class to operate on whole XML tree. This is useful but not always - sometimes generated code does not have XmlRootElement annotation sometimes you need unmarshall only part of tree. In that case you can use partial unmarshalling. To enable this behaviours you need set property partClass. Camel will pass this class to JAXB's unmarshaler.
Name of class used for fragment parsing. See more details at the fragment option.
XML namespace to use for fragment parsing. See more details at the fragment option.
When marshalling using JAXB or SOAP then the JAXB implementation will automatic assign namespace prefixes such as ns2 ns3 ns4 etc. To control this mapping Camel allows you to refer to a map which contains the desired mapping.
To use a custom xml stream writer.
To define the location of the schema
Class name to use when unmarshalling from XML to Java.
To use a custom binding factory
To enable pretty printing output nicely formatted. Is by default false.
Which json library to use such. Is by default xstream
Class name of the java type to use when unarmshalling
When marshalling a POJO to JSON you might want to exclude certain fields from the JSON output. With Jackson you can use JSON views to accomplish this. This option is to refer to the class which has JsonView annotations
If you want to marshal a pojo to JSON and the pojo has some fields with null values. And you want to skip these null values you can set this option to NOT_NULL
Used for JMS users to allow the JMSType header from the JMS spec to specify a FQN classname to use to unmarshal to.
Refers to a custom collection type to lookup in the registry to use. This option should rarely be used but allows to use different collection types than java.util.Collection based as default.
To unarmshal to a List of Map or a List of Pojo.
Whether to enable the JAXB annotations module when using jackson. When enabled then JAXB annotations can be used by Jackson.
To use custom Jackson modules com.fasterxml.jackson.databind.Module specified as a String with FQN class names. Multiple classes can be separated by comma.
To use custom Jackson modules referred from the Camel registry. Multiple modules can be separated by comma.
Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature com.fasterxml.jackson.databind.DeserializationFeature or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma
Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that matches a enum from com.fasterxml.jackson.databind.SerializationFeature com.fasterxml.jackson.databind.DeserializationFeature or com.fasterxml.jackson.databind.MapperFeature Multiple features can be separated by comma
Name of class to use when unarmshalling
The cipher algorithm to be used for encryption/decryption of the XML message content. The available choices are: XMLCipher.TRIPLEDES XMLCipher.AES_128 XMLCipher.AES_128_GCM XMLCipher.AES_192 XMLCipher.AES_192_GCM XMLCipher.AES_256 XMLCipher.AES_256_GCM XMLCipher.SEED_128 XMLCipher.CAMELLIA_128 XMLCipher.CAMELLIA_192 XMLCipher.CAMELLIA_256 The default value is MLCipher.TRIPLEDES
A String used as passPhrase to encrypt/decrypt content. The passPhrase has to be provided. If no passPhrase is specified a default passPhrase is used. The passPhrase needs to be put together in conjunction with the appropriate encryption algorithm. For example using TRIPLEDES the passPhase can be a Only another 24 Byte key
The XPath reference to the XML Element selected for encryption/decryption. If no tag is specified the entire payload is encrypted/decrypted.
A boolean value to specify whether the XML Element is to be encrypted or the contents of the XML Element false = Element Level true = Element Content Level
The cipher algorithm to be used for encryption/decryption of the asymmetric key. The available choices are: XMLCipher.RSA_v1dot5 XMLCipher.RSA_OAEP XMLCipher.RSA_OAEP_11 The default value is XMLCipher.RSA_OAEP
The key alias to be used when retrieving the recipient's public or private key from a KeyStore when performing asymmetric key encryption or decryption.
Refers to a KeyStore instance to lookup in the registry which is used for configuration options for creating and loading a KeyStore instance that represents the sender's trustStore or recipient's keyStore.
The password to be used for retrieving the private key from the KeyStore. This key is used for asymmetric decryption.
The digest algorithm to use with the RSA OAEP algorithm. The available choices are: XMLCipher.SHA1 XMLCipher.SHA256 XMLCipher.SHA512 The default value is XMLCipher.SHA1
The MGF Algorithm to use with the RSA OAEP algorithm. The available choices are: EncryptionConstants.MGF1_SHA1 EncryptionConstants.MGF1_SHA256 EncryptionConstants.MGF1_SHA512 The default value is EncryptionConstants.MGF1_SHA1
Whether to add the public key used to encrypt the session key as a KeyValue in the EncryptedKey structure or not.
Package name where your JAXB classes are located.
To overrule and use a specific encoding
Refers to an element strategy to lookup from the registry. An element name strategy is used for two purposes. The first is to find a xml element name for a given object and soap action when marshaling the object into a SOAP message. The second is to find an Exception class for a given soap fault name. The following three element strategy class name is provided out of the box. QNameStrategy - Uses a fixed qName that is configured on instantiation. Exception lookup is not supported TypeNameStrategy - Uses the name and namespace from the XMLType annotation of the given type. If no namespace is set then package-info is used. Exception lookup is not supported ServiceInterfaceStrategy - Uses information from a webservice interface to determine the type name and to find the exception class for a SOAP fault All three classes is located in the package name org.apache.camel.dataformat.soap.name If you have generated the web service stub code with cxf-codegen or a similar tool then you probably will want to use the ServiceInterfaceStrategy. In the case you have no annotated service interface you should use QNameStrategy or TypeNameStrategy.
SOAP version should either be 1.1 or 1.2. Is by default 1.1
When marshalling using JAXB or SOAP then the JAXB implementation will automatic assign namespace prefixes such as ns2 ns3 ns4 etc. To control this mapping Camel allows you to refer to a map which contains the desired mapping.
To validate against an existing schema. Your can use the prefix classpath: file: or http: to specify how the resource should by resolved. You can separate multiple schema files by using the '' character.
Sets an encoding to use. Will by default use the JVM platform default charset.
What data type to unmarshal as can either be org.w3c.dom.Node or java.lang.String. Is by default org.w3c.dom.Node
Whether or not all values must be quoted when writing them.
The quote symbol.
The quote escape symbol
The delimiter of values
The string representation of a null value. The default value is null
Whether or not the empty lines must be ignored. The default value is true
Whether or not the trailing white spaces must ignored. The default value is true
Whether or not the leading white spaces must be ignored. The default value is true
Whether or not the headers are disabled. When defined this option explicitly sets the headers as null which indicates that there is no header. The default value is false
Whether or not the header must be read in the first line of the test document The default value is false
The maximum number of record to read.
The String representation of an empty value
The line separator of the files The default value is to use the JVM platform line separator
The normalized line separator of the files The default value is \n
The comment symbol. The default value is
Whether the unmarshalling should produce an iterator that reads the lines on the fly or if all the lines must be read at one. The default value is false
Whether the unmarshalling should produce maps for the lines values instead of lists. It requires to have header (either defined or collected). The default value is false
Header length
Whether or not the trailing characters until new line must be ignored. The default value is false
Whether or not the record ends on new line. The default value is false
The padding character. The default value is a space
The escape character.
To enable pretty printing output nicely formatted. Is by default false.
Sets the encoding. Used for unmarshalling (JSON to XML conversion).
Specifies the name of the XML elements representing each array element. Used for unmarshalling (JSON to XML conversion).
Specifies the name of the top-level XML element. Used for unmarshalling (JSON to XML conversion). For example when converting 1 2 3 it will be output by default as 123. By setting this option or rootName you can alter the name of element 'a'.
Determines whether the resulting JSON will start off with a top-most element whose name matches the XML root element. Used for marshalling (XML to JSon conversion). If disabled XML string 12 turns into 'x: '1' 'y': '2' . Otherwise it turns into 'a': 'x: '1' 'y': '2' .
Flag to be tolerant to incomplete namespace prefixes. Used for unmarshalling (JSON to XML conversion). In most cases json-lib automatically changes this flag at runtime to match the processing.
Specifies the name of the top-level element. Used for unmarshalling (JSON to XML conversion). If not set json-lib will use arrayName or objectName (default value: 'o' at the current time it is not configurable in this data format). If set to 'root' the JSON string 'x': 'value1' 'y' : 'value2' would turn into value1value2 otherwise the 'root' element would be named 'o'.
Determines whether white spaces between XML elements will be regarded as text values or disregarded. Used for marshalling (XML to JSon conversion).
Determines whether leading and trailing white spaces will be omitted from String values. Used for marshalling (XML to JSon conversion).
Signals whether namespaces should be ignored. By default they will be added to the JSON output using xmlns elements. Used for marshalling (XML to JSon conversion).
Removes the namespace prefixes from XML qualified elements so that the resulting JSON string does not contain them. Used for marshalling (XML to JSon conversion).
With expandable properties JSON array elements are converted to XML as a sequence of repetitive XML elements with the local name equal to the JSON key for example: number: 123 normally converted to: 123 (where e can be modified by setting elementName) would instead translate to 123 if number is set as an expandable property Used for unmarshalling (JSON to XML conversion).
Adds type hints to the resulting XML to aid conversion back to JSON. Used for unmarshalling (JSON to XML conversion).
Whether to unmarshal request or response Is by default false
Sets the encoding to use
To use a custom XStream driver. The instance must be of type com.thoughtworks.xstream.io.HierarchicalStreamDriver
To refer to a custom XStream driver to lookup in the registry. The instance must be of type com.thoughtworks.xstream.io.HierarchicalStreamDriver
Mode for dealing with duplicate references The possible values are: NO_REFERENCES ID_REFERENCES XPATH_RELATIVE_REFERENCES XPATH_ABSOLUTE_REFERENCES SINGLE_NODE_XPATH_RELATIVE_REFERENCES SINGLE_NODE_XPATH_ABSOLUTE_REFERENCES
The user ID of the key in the PGP keyring used during encryption. Can also be only a part of a user ID. For example if the user ID is Test User then you can use the part Test User or to address the user ID.
User ID of the key in the PGP keyring used for signing (during encryption) or signature verification (during decryption). During the signature verification process the specified User ID restricts the public keys from the public keyring which can be used for the verification. If no User ID is specified for the signature verficiation then any public key in the public keyring can be used for the verification. Can also be only a part of a user ID. For example if the user ID is Test User then you can use the part Test User or to address the User ID.
Password used when opening the private key (not used for encryption).
Password used when opening the private key used for signing (during encryption).
Filename of the keyring; must be accessible as a classpath resource (but you can specify a location in the file system by using the file: prefix).
Filename of the keyring to use for signing (during encryption) or for signature verification (during decryption); must be accessible as a classpath resource (but you can specify a location in the file system by using the file: prefix).
Keyring used for signing/verifying as byte array. You can not set the signatureKeyFileName and signatureKeyRing at the same time.
This option will cause PGP to base64 encode the encrypted text making it available for copy/paste etc.
Adds an integrity check/sign into the encryption file. The default value is true.
Java Cryptography Extension (JCE) provider default is Bouncy Castle (BC). Alternatively you can use for example the IAIK JCE provider; in this case the provider must be registered beforehand and the Bouncy Castle provider must not be registered beforehand. The Sun JCE provider does not work.
Symmetric key encryption algorithm; possible values are defined in org.bouncycastle.bcpg.SymmetricKeyAlgorithmTags; for example 2 (= TRIPLE DES) 3 (= CAST5) 4 (= BLOWFISH) 6 (= DES) 7 (= AES_128). Only relevant for encrypting.
Compression algorithm; possible values are defined in org.bouncycastle.bcpg.CompressionAlgorithmTags; for example 0 (= UNCOMPRESSED) 1 (= ZIP) 2 (= ZLIB) 3 (= BZIP2). Only relevant for encrypting.
Signature hash algorithm; possible values are defined in org.bouncycastle.bcpg.HashAlgorithmTags; for example 2 (= SHA1) 8 (= SHA256) 9 (= SHA384) 10 (= SHA512) 11 (=SHA224). Only relevant for signing.
Controls the behavior for verifying the signature during unmarshaling. There are 4 values possible: optional: The PGP message may or may not contain signatures; if it does contain signatures then a signature verification is executed. required: The PGP message must contain at least one signature; if this is not the case an exception (PGPException) is thrown. A signature verification is executed. ignore: Contained signatures in the PGP message are ignored; no signature verification is executed. no_signature_allowed: The PGP message must not contain a signature; otherwise an exception (PGPException) is thrown.
To specify a specific compression between 0-9. -1 is default compression 0 is no compression and 9 is best compression.
If the zip file has more then one entry the setting this option to true allows to work with the splitter EIP to split the data using an iterator in a streaming mode.
If enabled then sending messages to the multicasts occurs concurrently. Note the caller thread will still wait until all messages has been fully processed before it continues. Its only the sending and processing the replies from the multicasts which happens concurrently.
Refers to an AggregationStrategy to be used to assemble the replies from the multicasts into a single outgoing message from the Multicast. By default Camel will use the last reply as the outgoing message. You can also use a POJO as the AggregationStrategy
This option can be used to explicit declare the method name to use when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used if there was no data to enrich. If this option is true then null values is used as the oldExchange (when no data to enrich) when using POJOs as the AggregationStrategy
Refers to a custom Thread Pool to be used for parallel processing. Notice if you set this option then parallel processing is automatic implied and you do not have to enable that option as well.
If enabled then Camel will process replies out-of-order eg in the order they come back. If disabled Camel will process replies in the same order as defined by the multicast.
Will now stop further processing if an exception or failure occurred during processing of an org.apache.camel.Exchange and the caused exception will be thrown. Will also stop if processing the exchange failed (has a fault message) or an exception was thrown and handled by the error handler (such as using onException). In all situations the multicast will stop further processing. This is the same behavior as in pipeline which is used by the routing engine. The default behavior is to not stop but continue processing till the end
Sets a total timeout specified in millis when using parallel processing. If the Multicast hasn't been able to send and process all replies within the given timeframe then the timeout triggers and the Multicast breaks out and continues. Notice if you provide a TimeoutAwareAggregationStrategy then the timeout method is invoked before breaking out. If the timeout is reached with running tasks still remaining certain tasks for which it is difficult for Camel to shut down in a graceful manner may continue to run. So use this option with a bit of care.
Uses the Processor when preparing the org.apache.camel.Exchange to be send. This can be used to deep-clone messages that should be send or any custom logic needed before the exchange is send.
Shares the org.apache.camel.spi.UnitOfWork with the parent and each of the sub messages. Multicast will by default not share unit of work between the parent exchange and each multicasted exchange. This means each sub exchange has its own individual unit of work.
If enabled then the aggregate method on AggregationStrategy can be called concurrently. Notice that this would require the implementation of AggregationStrategy to be implemented as thread-safe. By default this is false meaning that Camel synchronizes the call to the aggregate method. Though in some use-cases this can be used to archive higher performance when the AggregationStrategy is implemented as thread-safe.
Sets the on completion mode. The default value is AfterConsumer
Will only synchronize when the org.apache.camel.Exchange completed successfully (no errors).
Will only synchronize when the org.apache.camel.Exchange ended with failure (exception or FAULT message).
If enabled then the on completion process will run asynchronously by a separate thread from a thread pool. By default this is false meaning the on completion process will run synchronously using the same caller thread as from the route.
Refers to a custom Thread Pool to be used for parallel processing. Notice if you set this option then parallel processing is automatic implied and you do not have to enable that option as well.
Will use the original input body when an org.apache.camel.Exchange for this on completion. By default this feature is off.
Sets a reference to a RedeliveryPolicy to lookup in the org.apache.camel.spi.Registry to be used.
Sets a reference to a processor that should be processed before a redelivery attempt. Can be used to change the org.apache.camel.Exchange before its being redelivered.
Will use the original input message when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN body we use the original IN body instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN body. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN body is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. By default this feature is off.
Sets the maximum redeliveries x = redeliver at most x times 0 = no redeliveries -1 = redeliver forever
Sets the initial redelivery delay
Allow synchronous delayed redelivery.
Sets the back off multiplier
Turn on exponential backk off
Sets the collision avoidance factor
Turn on collision avoidance.
Sets the maximum delay between redelivery
Sets the logging level to use when retries has exhausted
Sets the logging level to use for logging retry attempts
Sets whether retry attempts should be logged or not. Can be used to include or reduce verbose.
Sets whether stack traces should be logged. Can be used to include or reduce verbose.
Sets whether stack traces should be logged when an retry attempt failed. Can be used to include or reduce verbose.
Sets whether handled exceptions should be logged or not. Can be used to include or reduce verbose.
Sets whether new exceptions should be logged or not. Can be used to include or reduce verbose. A new exception is an exception that was thrown while handling a previous exception.
Sets whether continued exceptions should be logged or not. Can be used to include or reduce verbose.
Sets whether exhausted exceptions should be logged or not. Can be used to include or reduce verbose.
Sets whether exhausted exceptions should be logged including message history or not (supports property placeholders). Can be used to include or reduce verbose.
Disables redelivery (same as setting maximum redeliveries to 0)
Sets the delay pattern with delay intervals.
Controls whether to allow redelivery while stopping/shutting down a route that uses error handling.
Sets the reference of the instance of org.apache.camel.spi.ExchangeFormatter to generate the log message from exchange.
Sets a reference to use for lookup the policy in the registry.
The endpoint uri for the external service to poll enrich from. You must use either uri or ref.
Refers to the endpoint for the external service to poll enrich from. You must use either uri or ref.
Timeout in millis when polling from the external service. The timeout has influence about the poll enrich behavior. It basically operations in three different modes: negative value - Waits until a message is available and then returns it. Warning that this method could block indefinitely if no messages are available. 0 - Attempts to receive a message exchange immediately without waiting and returning null if a message exchange is not available yet. positive value - Attempts to receive a message exchange waiting up to the given timeout to expire if a message is not yet available. Returns null if timed out The default value is -1 and therefore the method could block indefinitely and therefore its recommended to use a timeout value
Refers to an AggregationStrategy to be used to merge the reply from the external service into a single outgoing message. By default Camel will use the reply from the external service as outgoing message.
This option can be used to explicit declare the method name to use when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used if there was no data to enrich. If this option is true then null values is used as the oldExchange (when no data to enrich) when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used if there was an exception thrown while trying to retrieve the data to enrich from the resource. Setting this option to true allows end users to control what to do if there was an exception in the aggregate method. For example to suppress the exception or set a custom message body etc.
Reference to the Processor to lookup in the registry to use.
Delimiter used if the Expression returned multiple endpoints. Can be turned off using the value false. The default value is
If enabled then sending messages to the recipients occurs concurrently. Note the caller thread will still wait until all messages has been fully processed before it continues. Its only the sending and processing the replies from the recipients which happens concurrently.
Sets a reference to the AggregationStrategy to be used to assemble the replies from the recipients into a single outgoing message from the RecipientList. By default Camel will use the last reply as the outgoing message. You can also use a POJO as the AggregationStrategy
This option can be used to explicit declare the method name to use when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used if there was no data to enrich. If this option is true then null values is used as the oldExchange (when no data to enrich) when using POJOs as the AggregationStrategy
Refers to a custom Thread Pool to be used for parallel processing. Notice if you set this option then parallel processing is automatic implied and you do not have to enable that option as well.
Will now stop further processing if an exception or failure occurred during processing of an org.apache.camel.Exchange and the caused exception will be thrown. Will also stop if processing the exchange failed (has a fault message) or an exception was thrown and handled by the error handler (such as using onException). In all situations the recipient list will stop further processing. This is the same behavior as in pipeline which is used by the routing engine. The default behavior is to not stop but continue processing till the end
Ignore the invalidate endpoint exception when try to create a producer with that endpoint
If enabled then Camel will process replies out-of-order eg in the order they come back. If disabled Camel will process replies in the same order as defined by the recipient list.
Sets a total timeout specified in millis when using parallel processing. If the Recipient List hasn't been able to send and process all replies within the given timeframe then the timeout triggers and the Recipient List breaks out and continues. Notice if you provide a TimeoutAwareAggregationStrategy then the timeout method is invoked before breaking out. If the timeout is reached with running tasks still remaining certain tasks for which it is difficult for Camel to shut down in a graceful manner may continue to run. So use this option with a bit of care.
Uses the Processor when preparing the org.apache.camel.Exchange to be send. This can be used to deep-clone messages that should be send or any custom logic needed before the exchange is send.
Shares the org.apache.camel.spi.UnitOfWork with the parent and each of the sub messages. Recipient List will by default not share unit of work between the parent exchange and each recipient exchange. This means each sub exchange has its own individual unit of work.
Sets the maximum size used by the org.apache.camel.impl.ProducerCache which is used to cache and reuse producers when using this recipient list when uris are reused.
If enabled then the aggregate method on AggregationStrategy can be called concurrently. Notice that this would require the implementation of AggregationStrategy to be implemented as thread-safe. By default this is false meaning that Camel synchronizes the call to the aggregate method. Though in some use-cases this can be used to archive higher performance when the AggregationStrategy is implemented as thread-safe.
Name of header to remove
Name or pattern of headers to remove
Name or patter of headers to not remove
Name or pattern of properties to remove
Name or pattern of properties to not remove
Name of property to remove
Sets the size of the batch to be re-ordered. The default size is 100.
Sets the timeout for collecting elements to be re-ordered. The default timeout is 1000 msec.
Whether to allow duplicates.
Whether to reverse the ordering.
Whether to ignore invalid exchanges
Sets the capacity of the resequencer's inbound queue.
Sets minimum time to wait for missing elements (messages).
Whether to ignore invalid exchanges
To use a custom comparator
If true throws an exception when messages older than the last delivered message are processed
Reference to the rest-dsl
Mark the transaction for rollback only (cannot be overruled to commit)
Mark only last sub transaction for rollback only. When using sub transactions (if the transaction manager support this)
Message to use in rollback exception
Reference to the route builder instance
Reference to the routes in the xml dsl
Whether to auto start this route
Whether to slow down processing messages by a given delay in msec.
Sets the bean ref name of the error handler builder to use on this route
The group that this route belongs to; could be the name of the RouteBuilder class or be explicitly configured in the XML. May be null.
Whether handle fault is enabled on this route.
Whether message history is enabled on this route.
Reference to custom org.apache.camel.spi.RoutePolicy to use by the route. Multiple policies can be configured by separating values using comma.
To control how to shutdown the route.
To control how to shutdown the route.
To configure the ordering of the routes being started
Whether stream caching is enabled on this route.
Whether tracing is enabled on this route.
Sets the uri delimiter to use
Ignore the invalidate endpoint exception when try to create a producer with that endpoint
Sets the maximum size used by the org.apache.camel.impl.ProducerCache which is used to cache and reuse producers when using this recipient list when uris are reused.
Sets the sample period during which only a single Exchange will pass through.
Sets the sample message count which only a single Exchange will pass through after this many received.
Sets the time units for the sample period defaulting to seconds.
Sets the new exchange pattern of the Exchange to be used from this point forward
Name of message header to set a new value
Name of message header to set a new value
Name of exchange property to set a new value
Sets a reference to lookup for the comparator to use for sorting
If enabled then processing each splitted messages occurs concurrently. Note the caller thread will still wait until all messages has been fully processed before it continues. Its only processing the sub messages from the splitter which happens concurrently.
Sets a reference to the AggregationStrategy to be used to assemble the replies from the splitted messages into a single outgoing message from the Splitter. By default Camel will use the original incoming message to the splitter (leave it unchanged). You can also use a POJO as the AggregationStrategy
This option can be used to explicit declare the method name to use when using POJOs as the AggregationStrategy.
If this option is false then the aggregate method is not used if there was no data to enrich. If this option is true then null values is used as the oldExchange (when no data to enrich) when using POJOs as the AggregationStrategy
Refers to a custom Thread Pool to be used for parallel processing. Notice if you set this option then parallel processing is automatic implied and you do not have to enable that option as well.
When in streaming mode then the splitter splits the original message on-demand and each splitted message is processed one by one. This reduces memory usage as the splitter do not split all the messages first but then we do not know the total size and therefore the link org.apache.camel.ExchangeSPLIT_SIZE is empty. In non-streaming mode (default) the splitter will split each message first to know the total size and then process each message one by one. This requires to keep all the splitted messages in memory and therefore requires more memory. The total size is provided in the link org.apache.camel.ExchangeSPLIT_SIZE header. The streaming mode also affects the aggregation behavior. If enabled then Camel will process replies out-of-order eg in the order they come back. If disabled Camel will process replies in the same order as the messages was splitted.
Will now stop further processing if an exception or failure occurred during processing of an org.apache.camel.Exchange and the caused exception will be thrown. Will also stop if processing the exchange failed (has a fault message) or an exception was thrown and handled by the error handler (such as using onException). In all situations the splitter will stop further processing. This is the same behavior as in pipeline which is used by the routing engine. The default behavior is to not stop but continue processing till the end
Sets a total timeout specified in millis when using parallel processing. If the Splitter hasn't been able to split and process all the sub messages within the given timeframe then the timeout triggers and the Splitter breaks out and continues. Notice if you provide a TimeoutAwareAggregationStrategy then the timeout method is invoked before breaking out. If the timeout is reached with running tasks still remaining certain tasks for which it is difficult for Camel to shut down in a graceful manner may continue to run. So use this option with a bit of care.
Uses the Processor when preparing the org.apache.camel.Exchange to be send. This can be used to deep-clone messages that should be send or any custom logic needed before the exchange is send.
Shares the org.apache.camel.spi.UnitOfWork with the parent and each of the sub messages. Splitter will by default not share unit of work between the parent exchange and each splitted exchange. This means each splitted exchange has its own individual unit of work.
If enabled then the aggregate method on AggregationStrategy can be called concurrently. Notice that this would require the implementation of AggregationStrategy to be implemented as thread-safe. By default this is false meaning that Camel synchronizes the call to the aggregate method. Though in some use-cases this can be used to archive higher performance when the AggregationStrategy is implemented as thread-safe.
Whether this profile is the default thread pool profile
Sets the core pool size
Sets the maximum pool size
Sets the keep alive time for idle threads in the pool
Sets the maximum number of tasks in the work queue. Use -1 or Integer.MAX_VALUE for an unbounded queue
Whether idle core threads is allowed to timeout and therefore can shrink the pool size below the core pool size Is by default false
Sets the handler for tasks which cannot be executed by the thread pool.
To refer to a custom thread pool or use a thread pool profile (as overlay)
Sets the core pool size
Sets the maximum pool size
Sets the keep alive time for idle threads
Sets the keep alive time unit. By default SECONDS is used.
Sets the maximum number of tasks in the work queue. Use -1 or Integer.MAX_VALUE for an unbounded queue
Whether idle core threads is allowed to timeout and therefore can shrink the pool size below the core pool size Is by default false
Sets the thread name to use.
Sets the handler for tasks which cannot be executed by the thread pool.
Whether or not the caller should run the task when it was rejected by the thread pool. Is by default true
Sets the ExecutorService which could be used by throttle definition
Sets the time period during which the maximum request count is valid for
Enables asynchronous delay which means the thread will no block while delaying.
Whether or not the caller should run the task when it was rejected by the thread pool. Is by default true
Whether or not throttler throws the ThrottlerRejectedExecutionException when the exchange exceeds the request limit Is by default false
Reference to the exception instance to lookup from the registry to throw
Sets the optional ExchangePattern used to invoke this endpoint
Sets a reference to use for lookup the policy in the registry.
To refer to a custom data format to use as unmarshaller
Uri of the endpoint to use as wire tap
Reference of the endpoint to use as wire tap
Reference to a Processor to use for creating a new body as the message to use for wire tapping
Uses a custom thread pool
Uses a copy of the original exchange
Uses the Processor when preparing the org.apache.camel.Exchange to be send. This can be used to deep-clone messages that should be send or any custom logic needed before the exchange is send.
Width of the barcode
Height of the barcode
Image type of the barcode such as png
Barcode format such as QR-Code
Allows to turn lenient on the JXPathContext. When turned on this allows the JXPath expression to evaluate against expressions and message bodies which may be invalid / missing data. This option is by default false
Sets the class name of the result type (type from output)
The name of the language to use
Either a reference or a class name of the bean to use
Reference to bean to lookup in the registry
Name of method to call
Class name of the bean to use
Sets the class name of the result type (type from output)
The (start) token to use as tokenizer for example \n for a new line token
The end token to use as tokenizer if using start/end token pairs.
To inherit namepaces from a root/parent tag name
Name of header to tokenize instead of using the message body.
If the token is a regular expression pattern. The default value is false
Whether the input is XML messages. This option must be set to true if working with XML payloads.
Whether to include the tokens in the parts The default value is false
To group N parts together for example to split big files into chunks of 1000 lines.
Name of header to tokenize instead of using the message body.
The extraction mode. The available extraction modes are: i - injecting the contextual namespace bindings into the extracted token (default) w - wrapping the extracted token in its ancestor context u - unwrapping the extracted token to its child content t - extracting the text content of the specified element
To group N parts together
Name of class for document type The default value is org.w3c.dom.Document
Sets the class name of the result type (type from output) The default result type is NodeSet
Whether to use Saxon.
References to a custom XPathFactory to lookup in the registry
The XPath object model to use
Whether to log namespaces which can assist during trouble shooting
Name of header to use as input instead of the message body
Sets the class name of the result type (type from output) The default result type is NodeSet
Name of header to use as input instead of the message body
The HTTP verb such as GET or POST
Uri template of this REST service such as /id.
To define the content type what the REST service consumes (accept as input) such as application/xml or application/json. This option will override what may be configured on a parent level
To define the content type what the REST service produces (uses for output) such as application/xml or application/json This option will override what may be configured on a parent level
Sets the binding mode to use. This option will override what may be configured on a parent level The default value is auto
Whether to skip binding on output if there is a custom HTTP error code header. This allows to build custom error messages that do not bind to json / xml etc as success messages otherwise will do. This option will override what may be configured on a parent level
Whether to enable CORS headers in the HTTP response. This option will override what may be configured on a parent level The default value is false.
Sets the class name to use for binding from input to POJO for the incoming data This option will override what may be configured on a parent level
Sets the class name to use for binding from POJO to output for the outgoing data This option will override what may be configured on a parent level
To define the content type what the REST service consumes (accept as input) such as application/xml or application/json
To define the content type what the REST service produces (uses for output) such as application/xml or application/json
Sets the binding mode to use. The default value is auto
Sets the class name to use for binding from input to POJO for the incoming data
Sets the class name to use for binding from POJO to output for the outgoing data
Whether to skip binding on output if there is a custom HTTP error code header. This allows to build custom error messages that do not bind to json / xml etc as success messages otherwise will do.
Whether to enable CORS headers in the HTTP response. The default value is false.
The Camel Rest component to use for the REST transport such as restlet spark-rest. If no component has been explicit configured then Camel will lookup if there is a Camel component that integrates with the Rest DSL or if a org.apache.camel.spi.RestConsumerFactory is registered in the registry. If either one is found then that is being used.
The scheme to use for exposing the REST service. Usually http or https is supported. The default value is http
The hostname to use for exposing the REST service.
The port number to use for exposing the REST service. Notice if you use servlet component then the port number configured here does not apply as the port number in use is the actual port number the servlet component is using. eg if using Apache Tomcat its the tomcat http port if using Apache Karaf its the HTTP service in Karaf that uses port 8181 by default etc. Though in those situations setting the port number here allows tooling and JMX to know the port number so its recommended to set the port number to the number that the servlet engine uses.
Sets a leading context-path the REST services will be using. This can be used when using components such as SERVLET where the deployed web application is deployed using a context-path.
If no hostname has been explicit configured then this resolver is used to compute the hostname the REST service will be using.
Sets the binding mode to use. The default value is auto
Whether to skip binding on output if there is a custom HTTP error code header. This allows to build custom error messages that do not bind to json / xml etc as success messages otherwise will do.
Whether to enable CORS headers in the HTTP response. The default value is false.
Name of specific json data format to use. By default json-jackson will be used. Important: This option is only for setting a custom name of the data format not to refer to an existing data format instance.
Name of specific XML data format to use. By default jaxb will be used. Important: This option is only for setting a custom name of the data format not to refer to an existing data format instance.
Property key
Property value
Path of the rest service such as /foo
To define the content type what the REST service consumes (accept as input) such as application/xml or application/json. This option will override what may be configured on a parent level
To define the content type what the REST service produces (uses for output) such as application/xml or application/json This option will override what may be configured on a parent level
Sets the binding mode to use. This option will override what may be configured on a parent level The default value is auto
Whether to skip binding on output if there is a custom HTTP error code header. This allows to build custom error messages that do not bind to json / xml etc as success messages otherwise will do. This option will override what may be configured on a parent level
Whether to enable CORS headers in the HTTP response. This option will override what may be configured on a parent level The default value is false.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy