Hi Mark,
there are some ways to achieve what you want, but propagating the exception
in the same thread is not directly achievable with any async framework,
One way - asking:
Use Actors and `?` (ask) your backend for a response. The actor will
complete the future or it will contain a timeout.
Or y
Rafal,
Thanks for the clarification. The pattern you are describing works very
well if your entire application is Akka based. In that case there is no
need to externalize the exceptions, everything is handled internally. Rest
controllers are a different matter. My thought was that different
co
Hi Mark,
Rafal has already covered the reasoning and I just wanted to direct some
more information into this thread.
You have to remember that the exact model you ask for does not really fit
concurrent / distributed systems - exceptions and stack traces are
inherently bound to a thread - the one ex
This is not how things work in Akka-land :) Exceptions thrown in an Actors
receive method are reported to it's supervisor actor which may choose to
escalate it (among other choices), but that means that the supervisor
itself terminates abnormally throwing an exception that is passed in turn
to
