Package org.apache.pekko.persistence
Interface Protocol.Message
-
- All Superinterfaces:
NoSerializationVerificationNeeded
- All Known Subinterfaces:
JournalProtocol.Message
,JournalProtocol.Request
,JournalProtocol.Response
,SnapshotProtocol.Message
,SnapshotProtocol.Request
,SnapshotProtocol.Response
- All Known Implementing Classes:
DeleteMessagesFailure
,DeleteMessagesSuccess
,DeleteSnapshotFailure
,DeleteSnapshotsFailure
,DeleteSnapshotsSuccess
,DeleteSnapshotSuccess
,JournalProtocol.DeleteMessagesTo
,JournalProtocol.LoopMessageSuccess
,JournalProtocol.RecoverySuccess
,JournalProtocol.ReplayedMessage
,JournalProtocol.ReplayMessages
,JournalProtocol.ReplayMessagesFailure
,JournalProtocol.WriteMessageFailure
,JournalProtocol.WriteMessageRejected
,JournalProtocol.WriteMessages
,JournalProtocol.WriteMessagesFailed
,JournalProtocol.WriteMessagesSuccessful$
,JournalProtocol.WriteMessageSuccess
,SaveSnapshotFailure
,SaveSnapshotSuccess
,SnapshotProtocol.DeleteSnapshot
,SnapshotProtocol.DeleteSnapshots
,SnapshotProtocol.LoadSnapshot
,SnapshotProtocol.LoadSnapshotFailed
,SnapshotProtocol.LoadSnapshotResult
,SnapshotProtocol.SaveSnapshot
- Enclosing class:
- Protocol
public static interface Protocol.Message extends NoSerializationVerificationNeeded
INTERNAL API.Internal persistence extension messages extend this trait.
Helps persistence plugin developers to differentiate internal persistence extension messages from their custom plugin messages.
Journal messages need not be serialization verified as the Journal Actor should always be a local Actor (and serialization is performed by plugins). One notable exception to this is the shared journal used for testing.