camel-web3j-kafka-connector sink configuration

Required Sets the node address used to communicate.

Contract address or a list of addresses.

The address the transaction is send from.

The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.

If true it returns the full transaction objects, if false only the hashes of the transactions.

The maximum gas allowed in this block.

A transaction privateFor nodes with public keys in a Quorum network.

If true, this will support Quorum API.

The address the transaction is directed to.

The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.

Topics are order-dependent. Each topic can also be a list of topics. Specify multiple topics separated by comma.

The preconfigured Web3j object.

Contract address.

The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.

Hash of the block where this transaction was in.

A random hexadecimal(32 bytes) ID identifying the client.

The compiled code of a contract OR the hash of the invoked method signature and encoded parameters.

The local database name.

The filter id to use.

Gas price used for each paid gas.

A hexadecimal string representation (32 bytes) of the hash rate.

The header’s pow-hash (256 bits) used for submitting a proof-of-work solution.

The transactions/uncle index position in the block.

The key name in the database.

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.

The mix digest (256 bits) used for submitting a proof-of-work solution.

The nonce found (64 bits) used for submitting a proof-of-work solution.

Operation to use.

The transaction index position withing a block.

The priority of a whisper message.

Message to sign by calculating an Ethereum specific signature.

The signed transaction data for a new message call transaction or a contract creation for signed transactions.

The source code to compile.

The information about a transaction requested by transaction hash.

The time to live in seconds of a whisper message.

The value sent within a transaction.

Contract address or a list of addresses.

Default configuration.

The address the transaction is send from.

The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.

If true it returns the full transaction objects, if false only the hashes of the transactions.

The maximum gas allowed in this block.

A transaction privateFor nodes with public keys in a Quorum network.

If true, this will support Quorum API.

The address the transaction is directed to.

The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.

Topics are order-dependent. Each topic can also be a list of topics. Specify multiple topics separated by comma.

The preconfigured Web3j object.

Contract address.

The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.

Hash of the block where this transaction was in.

A random hexadecimal(32 bytes) ID identifying the client.

The compiled code of a contract OR the hash of the invoked method signature and encoded parameters.

The local database name.

The filter id to use.

Gas price used for each paid gas.

A hexadecimal string representation (32 bytes) of the hash rate.

The header’s pow-hash (256 bits) used for submitting a proof-of-work solution.

The transactions/uncle index position in the block.

The key name in the database.

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.

The mix digest (256 bits) used for submitting a proof-of-work solution.

The nonce found (64 bits) used for submitting a proof-of-work solution.

Operation to use.

The transaction index position withing a block.

The priority of a whisper message.

Message to sign by calculating an Ethereum specific signature.

The signed transaction data for a new message call transaction or a contract creation for signed transactions.

The source code to compile.

The information about a transaction requested by transaction hash.

The time to live in seconds of a whisper message.

The value sent within a transaction.

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.