Description
Ideally to be enforced by running on a different (isolated) thread.
Yet we are using the fork-join common pool, which provides no such guarantee.
Currently an async execution might eventually run on the same thread as the caller, and hence participate in the same transaction as the caller. The framework must prevent this from happening.
Attachments
Issue Links
- is depended upon by
-
CAUSEWAY-2578 No injection points resolved on entity collections (both persistence stacks)
-
- Closed
-