open fun recordTransactions(notifyVault: Boolean, txs: Iterable<SignedTransaction>): Unit
Stores the given SignedTransactions in the local transaction storage and then sends them to the vault for further processing if notifyVault is true. This is expected to be run within a database transaction.
As of platform version TWO_PHASE_FINALITY also performs signature verification and will throw an IllegalStateException with details of the cause of error upon failure. Of course, you should not be recording transactions to the ledger that are not fully signed. It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
txs - The transactions to record.
notifyVault - indicate if the vault should be notified for the update.
open fun recordTransactions(notifyVault: Boolean, first: SignedTransaction, vararg remaining: SignedTransaction): Unit
Stores the given SignedTransactions in the local transaction storage and then sends them to the vault for further processing if notifyVault is true. This is expected to be run within a database transaction.
As of platform version TWO_PHASE_FINALITY also performs signature verification and will throw an IllegalStateException with details of the cause of error upon failure. Of course, you should not be recording transactions to the ledger that are not fully signed. It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
abstract fun recordTransactions(statesToRecord: StatesToRecord, txs: Iterable<SignedTransaction>): Unit
Stores the given SignedTransactions in the local transaction storage and then sends them to the vault for further processing if statesToRecord is not StatesToRecord.NONE. This is expected to be run within a database transaction.
As of platform version TWO_PHASE_FINALITY also performs signature verification and will throw an IllegalStateException with details of the cause of error upon failure. Of course, you should not be recording transactions to the ledger that are not fully signed. It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
txs - The transactions to record.
statesToRecord - how the vault should treat the output states of the transaction.
open fun recordTransactions(first: SignedTransaction, vararg remaining: SignedTransaction): Unitopen fun recordTransactions(txs: Iterable<SignedTransaction>): Unit
Stores the given SignedTransactions in the local transaction storage and then sends them to the vault for further processing. This is expected to be run within a database transaction.
As of platform version TWO_PHASE_FINALITY also performs signature verification and will throw an IllegalStateException with details of the cause of error upon failure. Of course, you should not be recording transactions to the ledger that are not fully signed. It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.