Levi Ramsey
Levi Ramsey
A sort of related observation is that it's not at all clear what the difference between a `Receive` and a `Behavior` is. A `Receive` seems to just be a `Behavior`...
Have not yet adjusted any of the tests ~~or docs~~ for the new `PersistenceProbe` API, btw.
Basically just docs (including adding a testing section for durable state in general, covering some of the other approaches). The code stuff should be OK to review now. (or should...
For the doc structure, I'm thinking to make `typed/persistence-testing.md` be like `typed/testing.md` with links to the different options (as well as mentioning explicitly that in many cases the event-handling logic...
For now, just adding the section to typed (event-sourced) persistence. Documenting the testing of durable state behaviors in general is a gap in the docs (AFAIK, the main way before...
I try to enforce a domain distinction between Java Duration is for things that aren't concurrency-related (e.g. ignore events older than such-and-such time) and Scala Duration is for concurrency-related timings....
The `AsyncResultSet` which the Java client returns has a `wasApplied` method which is the value of the `[applied]` column: it's always `true` for unconditional queries. So there are three options...
Wouldn't durable state only really be expected to expose the durable state queries? The JDBC plugin doesn't seem to implement `eventsBy*` for durable state.
This appears to be caused by an interaction between #2695 and IBM MQ.
Seems completed?