States and statuses
A core element of the CDL Smart Contract view is that Corda states can have different statuses. When a state has a particular status, there are different restrictions on the form of the state and the transitions that state can make.
ContractStates
which require a status property should implement the StatusState
interface. This requires a val status: Status?
property to be implemented by the state.
In ContractUtils
, the interfaces for StatusState
and Status
are defined as follows:
/**
* The StatusState interface should be implemented for all [ContractState]s that require a status field.
*
* [status] is nullable so that when there is no input or output state in a transaction, the status can be represented as [null]
*
*/
interface StatusState: ContractState {
val status: Status?
}
/**
* Statuses are defined as enum classes in the StatusState which should implement this Status interface.
*/
@CordaSerializable
interface Status
You can see that status
is nullable because the intention is to represent no state as a status null
. For example, when defining Paths allowed in transactions which have no input state, you define the input status as null
so you can map null
-> allowed Paths when there is no input state.
These interfaces are used to define the AgreementState
and the enum set of statuses based on the CDL status states:
AgreementState.kt:
@BelongsToContract(AgreementContract::class)
data class AgreementState(override val status: AgreementStatus?,
val buyer: Party,
val seller: Party,
val goods: String,
val price: Amount<Currency>,
val proposer: Party,
val consenter: Party,
val rejectionReason: String? = null,
val rejectedBy: Party?= null,
override val participants: List<AbstractParty> = listOf(buyer, seller),
override val linearId: UniqueIdentifier = UniqueIdentifier()) : LinearState, StatusState
enum class AgreementStatus: Status {
PROPOSED,
REJECTED,
AGREED
}
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.