Specifies the data type to which the data will be unmarshalled. For data formats that require configuration, the format's tab provides the property fields to configure the marshaller.

Because the GZip, Serialization, String, and Zip data formats are part of the Camel core, you need not add dependencies for them in your Mavenpom.xml file to use them. However, to use any of the other supported data formats, you must add a dependency on the component that implements the data format (for example, camel-protobuf, camel-xmlbeans, camel-flatpack, camel-base64, camel-xmlrpc, camel-zipfile, and so on) in your Mavenpom.xml file.

Specifies a unique identifier for the endpoint.

The tooling automatically generates an id for a node when it is created, but you can remove that id or replace it with your own. The Camel debugger requires all nodes with a breakpoint set to have a unique id.

You can use the id to refer to endpoints in your Camel XML file.

Specifies the maximum line length.

Specifies the line separator to use.

Specifies the charset to use. The default is platform-specific.

Species whether to ignore invalid records. The default is false.

Specifies a fully qualified class name that explicitly defines the type to use for unmarshalling. For example, you might enter com.mycompany.MyOrder

You must use either this property or Packages, but not both.

Species the language name of the locale whose date and number format will be used. If not specified, the unmarshaller determines and uses the formatting of a default language name. Valid values are the two-letter abbreviation of the language name, in lower case. For example,

For an exhaustive list of language names, see Codes for the Representation of Names of Languages

Specifies the packages to use for unmarshalling. A package contains a defined model with required annotations properly associated for each class in the model. For example, you might enter com.mycompany.

When specifying multiple packages, separate them with a comma (,).

You must use either this property or Class Type, but not both.

Specifies whether to allow missing column names in the header line.

The default is Disabled for formats DEFAULT, RFC4180, MYSQL, and TDF, but True for EXCEL. (See Format Name for available reference formats.)

Specifies the character to use to mark the start of a comment line.

The default is null.

Specifies the character to use for the value delimiter, typically ,, ;, or \t. The line break character causes an IllegalArguementException.

The default is , for formats DEFAULT, RFC4180, and EXCEL, but \t for MYSQL and TDF. (See Format Name for available reference formats.)

Specifies the character to use as the escape character.

The default is null, except for MYSQL, for which the default is \\. (See Format Name for available reference formats.)

Specifies the name of the reference format to use for parsing input. Predefined reference format options are:

Specifies the column names to use to address values in the CSV records. If your CSV source contains a first record that also defines column names, enable the Skip Header Record property.

The default is null.

Specifies whether empty lines between records are ignored or turned into empty records.

The default is False for formats RFC4180, EXCEL, MYSQL and TDF, which results in empty lines becoming empty records, but True for DEFAULT, which results in empty lines being ignored. (See Format Name for available reference formats.)

Specifies whether spaces surrounding values are trimmed or included as part of the value.

The default is False for formats DEFAULT, RFC4180, EXCEL, and MYSQL, which results in including empty spaces with values, but True for TDF, which results in empty lines being ignored/trimmed. (See Format Name for available reference formats.)

Specifies a reference to the record converter to use for unmarshalling when Use Maps is Disabled.

The default is null.

Specifies the character or characters to use for the record separator. If not specified, uses the default of the reference format.

The default is \r\n for formats DEFAULT, RFC4180, EXCEL, and TDF, but \n for MYSQL. (See Format Name for available reference formats.)

Specifies whether the unmarshaller produces maps, instead of lists, for line values. When enabled, the input must have a header line (either defined or collected).

The default is False.

Specifies the flatpack pzmap configuration file to use to configure the structure of the input. If not specified, the configuration of the input defaults to Delimited.

Specifies the encoding to use when unmarshalling data. Valid values include:

With no value specified, Red Hat JBoss Fuse Tooling for Eclipse defaults to the encoding used by JAXB.

Not applicable. Specifies the id of the <util:map> that contains custom namespace mapping specifications.

The JAXB implementation auto assigns namespace prefixes (such as n1,n2, n3,...) to namespaces when marshalling JAXB or SOAP. To use your own custom prefixes or to eliminate prefixes, you need to create and reference a <util:map> in your camelContext. For example:

<util:map id="myMap">
 <!-- Assign the prefix soap to the soap namespace -->   
   <entry key="http://www.w3.org/2003/05/soap-envelope" value="soap" />
 <!-- Eliminate any prefix from our own namespace -->
   <entry key="http://www.mycompny.com/foo/2" value="" />
</util:map>

Not applicable. Specifies the symmetric key encryption algorithm to use for encryption. Valid values are defined in org.bouncycastle.bcpg.SymmetricKeyAlgorithmTags. The default is 3 (SymmetricKeyAlgorithmTags.CAST5).

Some example values are:

Not applicable. Specifies the compression algorithm used for encryption. Valid values are defined in org.bouncycastle.bcpg.CompressionAlgorithmTags. The default is 1 (CompressionAlgorithmTags.ZIP).

Some example values are:

Not applicable. Specifies the hash algorithm used for signing during encryption. Valid values are defined in org.bouncycastle.bcpg.HashAlgorithmTags. The default is 2 (HashAlgorithmTags.SHA10).

Some example values are:

Specifies an optional name of the keyring file to use for signing during encryption or for signature verification during decryption. This file must be accessible as a classpath resource, but you can specify its location in the file system using the file: prefix.

Do not set this option when Signature Key Ring is set.

Specifies the keyring to use for signing during encryption or during signature verification.

Do not set this option when Signature Key File Name is set.

Specifies an optional user ID for the key in the PGP keyring used for signing during encryption or for signature verification during decryption.

During the signature verification process, the specified Signature Key Userid prevents public keys in the public keyring being used for verification. If not specified, any public key in the public keyring can be used for verification.

You can also specify a portion of the user ID. For example, for user ID "TEST USER <test@camel.com>", you can specify the "Test User" part or the "test@camel.com" part.

Controls the behavior of signature verification during decryption.

Valid values are:

The default is optional.

Species the digest algorithm to use with the RSA OAEP algorithm. Default is XMLCipher.SHA1. Valid values are:

Specifies the cipher algorithm to use to encrypt the asymmetric key. The default is XMLCipher.RSA_OAEP [Camel 2.12]. Valid values are:

Asymmetric key encryption is enabled when either this property or the Recipient Key Alias property is set.

Specifies the MFG algorithm to use with the RSA OAEP algorithm, when performing asymmetric key encryption. The default is EncryptionConstants.MFG1_SHA1. Valid values are:

Specifies the cipher algorithm to use for encrypting message content. Valid values a:re:

Specifies the encoding to use when unmarshalling data. Valid values include:

With no value specified, Red Hat JBoss Fuse Tooling for Eclipse defaults to the encoding used by JAXB.

Specifies a reference to a map containing the namespace mapping to use when unmarshalling using JAXB or SOAP. This option enables you to override the default behavior of the JAXB implementation, which automatically assigns its own prefixes to namespaces.

First you define the map with mappings made up of key/value pair entries, each of which specifies a namespace (key) and prefix (value) to use for it, and assign the map an id to use as the Namespace Prefix Ref.

NOTE: This option requires that JAXB-RI 2.1 or higher (from SUN) be on the classpath.

Specifies the character set to use for encoding. Valid values include:

With no value specified, Red Hat JBoss Fuse Tooling for Eclipse defaults to the encoding used by the platform.

Enables/disables the production of maps, instead of lists, for line values. The default is Disabled, which causes the unmarshaller to produce lists instead of maps.

When enabling this option to produce maps instead of lists, headers must be enabled and either defined or collected.

Enables/disables the production of maps, instead of lists, for line values. The default is Disabled, which causes the unmarshaller to produce lists instead of maps.

When enabling this option to produce maps instead of lists, headers must be enabled and either defined or collected.

Enables/disables the production of maps, instead of lists, for line values. The default is Disabled, which causes the unmarshaller to produce lists instead of maps.

When enabling this option to produce maps instead of lists, headers must be enabled and either defined or collected.

Specifies the name of the top-level XML element. The default is 'a'

For example, [1,2,3] is converted to <a><e>1</e><e>2</e><e>3</e><a> by default. By setting this property or Root Name, you can change the name of element 'a'.

Specifies the name of the XML element that represents each array element. The default is 'e'.

Specifies the encoding for the call to the XMLSerializer.write()method, so it's used only when generating XML.

Specifies expandable properties that alter the way JSON array elements are converted to XML. Using 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, if number is set as an expandable property, the array {number:1,2,3}, normally converted to <number>:<e>1</e><e>2</e><e>3</e></number>, will instead be converted to <number>1</number><number>2</number><number>3</number>.

Applies to marshalling only.

Specifies whether to tolerate incomplete namespace prefixes. The default is false.

In most cases, json-lib automatically changes this property at runtime to match the processing.

Applies to marshalling only.

Specifies the name of the top-level element when converting any JSON construct (object, array, null) to XML.

If not set, json-lib uses arrayName or objectName (default value of'o').

If set to 'root', the JSON string {'x':'value1','y':'value2'} is converted to <root><x>value1</x><y>value2</y></root>; otherwise, the 'root' element would be named 'o'.

Applies to marshalling only.

Specifies whether to add type hints to the resulting XML to aid conversion back to JSON. The default is YES.

Valid values are:

Not Applicable.

When enabled, iteratively unmarshals multiple entries in a zip file to their original file format. The default is Disabled.