...
Name | Default Value | Description |
---|---|---|
codec | null | As of 1.3 or later you can refer to a named ProtocolCodecFactory instance in your Registry such as your Spring ApplicationContext which is then used for the marshalling |
textline | false | Only used for TCP. If no codec is specified then you can use this flag in 1.3 or later to indicate a text line based codec; if not specified or the value is false then Object Serialization is assumed over TCP. |
sync | false/true | As of 1.3 or later you can configure the exchange pattern to be either InOnly (default) or InOut. Setting sync=true means a synchronous exchange (InOut), where the client can read the response from MINA (The exchange out message). The default value has changed in Camel 1.5 to true. In older releases the default value is false. |
lazySessionCreation | false | As of 1.3 or later session can be lazy created to avoid exceptions if the remote server is not up and running when the Camel producer is started. |
timeout | 30000 | As of 1.3 or later you can configure the timeout while waiting for a response from a remote server. The timeout unit is in millis, so 60000 is 60 seconds. The timeout is only used for MinaProducer. |
encoding | JVM Default | As of 1.3 or later you can configure the encoding (is a charset name) to use for the TCP textline codec and the UDP protocol. If not provided Camel will use the JVM default Charset. |
transferExchange | false | Only used for TCP. As of 1.3 or later you can transfer the exchange over the wire instead of just the body. The following fields is transferedtransferred: in body, out body, fault body, in headers, out headers, fault headers, exchange properties, exchange exception. |
minaLogger | false | As of 1.3 or later you can enable Apache MINA logging filter. Apache MINA uses slf4j logging at INFO level to log all input and output. |
...