Web3j Ethereum Blockchain

Interact with Ethereum nodes using web3j client API.

Metadata

Property	Value
Scheme	`web3j`
Support Level	Stable
Labels	blockchain
Version	4.10.2

Maven Dependency

<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-web3j</artifactId>
    <version>4.10.2</version>
</dependency>

Endpoint Properties

Name	Type	Required	Default	Description
`nodeAddress`	string	✓		Sets the node address used to communicate
`addresses`	array			Contract address or a list of addresses.
`fromAddress`	string			The address the transaction is send from
`fromBlock`	string		`latest`	The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.
`fullTransactionObjects`	boolean		`false`	If true it returns the full transaction objects, if false only the hashes of the transactions.
`gasLimit`	object			The maximum gas allowed in this block.
`privateFor`	array			A transaction privateFor nodes with public keys in a Quorum network
`quorumAPI`	boolean		`false`	If true, this will support Quorum API.
`toAddress`	string			The address the transaction is directed to.
`toBlock`	string		`latest`	The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.
`topics`	string			Topics are order-dependent. Each topic can also be a list of topics. Specify multiple topics separated by comma.
`web3j`	object			The preconfigured Web3j object.
`bridgeErrorHandler`	boolean		`false`	Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.
`exceptionHandler`	object			To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.
`exchangePattern`	object			Sets the exchange pattern when the consumer creates an exchange.
`address`	string			Contract address.
`atBlock`	string		`latest`	The block number, or the string latest for the last mined block or pending, earliest for not yet mined transactions.
`blockHash`	string			Hash of the block where this transaction was in.
`clientId`	string			A random hexadecimal(32 bytes) ID identifying the client.
`data`	string			The compiled code of a contract OR the hash of the invoked method signature and encoded parameters.
`databaseName`	string			The local database name.
`filterId`	object			The filter id to use.
`gasPrice`	object			Gas price used for each paid gas.
`hashrate`	string			A hexadecimal string representation (32 bytes) of the hash rate.
`headerPowHash`	string			The header's pow-hash (256 bits) used for submitting a proof-of-work solution.
`index`	object			The transactions/uncle index position in the block.
`keyName`	string			The key name in the database.
`mixDigest`	string			The mix digest (256 bits) used for submitting a proof-of-work solution.
`nonce`	string			The nonce found (64 bits) used for submitting a proof-of-work solution.
`operation`	string		`transaction`	Operation to use.
`position`	object			The transaction index position withing a block.
`priority`	object			The priority of a whisper message.
`sha3HashOfDataToSign`	string			Message to sign by calculating an Ethereum specific signature.
`signedTransactionData`	string			The signed transaction data for a new message call transaction or a contract creation for signed transactions.
`sourceCode`	string			The source code to compile.
`transactionHash`	string			The information about a transaction requested by transaction hash.
`ttl`	object			The time to live in seconds of a whisper message.
`value`	object			The value sent within a transaction.
`lazyStartProducer`	boolean		`false`	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.