The payload type the consuming definition's parser produces
Optional ReadonlyaggregateID of the aggregate the event concerns, when supplied.
Optional ReadonlyaggregateVersion of the aggregate the event concerns, when supplied.
Optional ReadonlycausationID of the event that directly caused this one, when propagated.
Optional ReadonlycorrelationID of the chain root this event descends from, when propagated.
ReadonlydataThe event payload, as the producer published it.
ReadonlyidProducer-assigned event identity (runtime.uuid()).
ReadonlyoccurredPublish time as an ISO-8601 string (new Date(runtime.now()).toISOString()).
ReadonlytypeThe definition's semantic event name.
ReadonlyversionThe definition's contract version.
The wire shape of a published integration event.
occurredAtis an ISO-8601 string, not aDate: the in-memory broker'sJsonSerializerround-trips payloads throughJSON.parse, so aDatewould arrive at the consumer as a string regardless of what the producer put in — declaring the field a string is the honest type on every transport. It is namedoccurredAt(notoccurredOn, theDate-typed field the events-pluginDomainEventcarries) so the two cannot be conflated.Unknown extra top-level fields are allowed by the consumer's structural check, so an additive envelope change on a later framework version is not a breaking deployment.
Since
0.6.0