Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
StatusMessage should be associated with transactionUid + sequence, not just transactionUid #88
There can be many interactions within a single transaction. Most notably this occurs when the WrapperFactory is used to invoke an action on a collection of objects; each of these is a separate interaction execution within the overall transaction, and will emit its own interaction execution through the PublisherService.
If we want to associate StatusMessage's with a particular interaction execution (when there are many), then the StatusMessage API (and corresponding entity) need to be extended in order to use both parts of the primary key of PublishedEvent.