Application event (or command).
Sequence number that is generated when messages are written to the journal. Can also be used for detecting duplicates, in special cases.
time the input message was added to the event log.
Id of the event processor that stored (and emitted) this message.
Whether or not an acknowledgement should be written to the journal during
(or after) delivery of this message by a org.eligosource.eventsourced.core.Channel.
Used by event processors to indicate a series of output messages (that are derived
from a single input message). In this case, output messages 1 to n-1 should have ack
set to false
and only output message n should have ack
set to true
(default).
If an acknowledgement has been written for a series, all messages of that series will
be ignored by the corresponding channel during a replay, otherwise all of them will
be delivered again.
Whether or not an acknowledgement should be written to the journal during (or after) delivery of this message by a org.eligosource.eventsourced.core.Channel.
Whether or not an acknowledgement should be written to the journal during
(or after) delivery of this message by a org.eligosource.eventsourced.core.Channel.
Used by event processors to indicate a series of output messages (that are derived
from a single input message). In this case, output messages 1 to n-1 should have ack
set to false
and only output message n should have ack
set to true
(default).
If an acknowledgement has been written for a series, all messages of that series will
be ignored by the corresponding channel during a replay, otherwise all of them will
be delivered again.
Should be called by org.eligosource.eventsourced.core.Channel destinations to (positively or negatively) confirm the receipt of this event message.
Should be called by org.eligosource.eventsourced.core.Channel destinations to (positively or negatively) confirm the receipt of this event message. Destinations may also delegate this call other actors or threads.
true
for a positive receipt confirmation, false
for a negative one.
Application event (or command).
Id of the event processor that stored (and emitted) this message.
Sequence number that is generated when messages are written to the journal.
Sequence number that is generated when messages are written to the journal. Can also be used for detecting duplicates, in special cases.
time the input message was added to the event log.
Returns a copy of this message with an updated ack
value.
Returns a copy of this message with an updated event
value.
A message for communicating application events. Application events are not interpreted by the eventsourced library and can have any type. Since the library doesn't make any assumptions about the structure and semantics of
event
, applications may also choose to send commands with org.eligosource.eventsourced.core.Messages. In other words, the library can be used for both, event-sourcing and command-sourcing.Messages sent to an org.eligosource.eventsourced.core.Eventsourced processor are called input messages. Processors process input messages and optionally emit (or send) output messages to one or more destinations, usually via org.eligosource.eventsourced.core.Channels. Output messages should be derived from input messages using the
copy(...)
method. Processors may also reply to initial senders using the actor's currentsender
reference.Application event (or command).
Sequence number that is generated when messages are written to the journal. Can also be used for detecting duplicates, in special cases.
time the input message was added to the event log.
Id of the event processor that stored (and emitted) this message.
Whether or not an acknowledgement should be written to the journal during (or after) delivery of this message by a org.eligosource.eventsourced.core.Channel. Used by event processors to indicate a series of output messages (that are derived from a single input message). In this case, output messages 1 to n-1 should have
ack
set tofalse
and only output message n should haveack
set totrue
(default). If an acknowledgement has been written for a series, all messages of that series will be ignored by the corresponding channel during a replay, otherwise all of them will be delivered again.