ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-05-31 06:31:08 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Update JavaDoc.

Browse Source
This commit is contained in:
Jose Coll 2023-03-30 09:08:09 +01:00
parent 4beeb470df
commit 18690dba94
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
core/src/main/kotlin/net/corda/core/node/ServiceHub.kt
View File

@ -209,7 +209,7 @@ interface ServiceHub : ServicesForResolution {
* [IllegalStateException] with details of the cause of error upon failure. * [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. * 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 * It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property
* "signature.verification.disabled" to true upon node start-up. * "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
* *
* @param txs The transactions to record. * @param txs The transactions to record.
* @param notifyVault indicate if the vault should be notified for the update. * @param notifyVault indicate if the vault should be notified for the update.
@ -226,7 +226,7 @@ interface ServiceHub : ServicesForResolution {
* [IllegalStateException] with details of the cause of error upon failure. * [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. * 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 * It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property
* "signature.verification.disabled" to true upon node start-up. * "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
*/ */
fun recordTransactions(notifyVault: Boolean, first: SignedTransaction, vararg remaining: SignedTransaction) { fun recordTransactions(notifyVault: Boolean, first: SignedTransaction, vararg remaining: SignedTransaction) {
recordTransactions(notifyVault, listOf(first, *remaining)) recordTransactions(notifyVault, listOf(first, *remaining))
@ -241,7 +241,7 @@ interface ServiceHub : ServicesForResolution {
* [IllegalStateException] with details of the cause of error upon failure. * [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. * 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 * It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property
* "signature.verification.disabled" to true upon node start-up. * "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
* *
* @param txs The transactions to record. * @param txs The transactions to record.
* @param statesToRecord how the vault should treat the output states of the transaction. * @param statesToRecord how the vault should treat the output states of the transaction.
@ -256,7 +256,7 @@ interface ServiceHub : ServicesForResolution {
* [IllegalStateException] with details of the cause of error upon failure. * [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. * 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 * It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property
* "signature.verification.disabled" to true upon node start-up. * "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
* *
*/ */
fun recordTransactions(first: SignedTransaction, vararg remaining: SignedTransaction) { fun recordTransactions(first: SignedTransaction, vararg remaining: SignedTransaction) {
@ -271,7 +271,7 @@ interface ServiceHub : ServicesForResolution {
* [IllegalStateException] with details of the cause of error upon failure. * [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. * 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 * It is possible, but not recommended, to revert to non-signature verification behaviour by setting the system property
* "signature.verification.disabled" to true upon node start-up. * "net.corda.recordtransaction.signature.verification.disabled" to true upon node start-up.
* *
*/ */
fun recordTransactions(txs: Iterable<SignedTransaction>) { fun recordTransactions(txs: Iterable<SignedTransaction>) {