Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow application-specific information in Handler Execution Exceptions #1079

abuijze opened this issue May 1, 2019 · 0 comments


None yet
2 participants
Copy link

commented May 1, 2019

When using AxonServer and an exception is thrown from an @CommandHandler or @QueryHandler, this exception gets translated to a generic exception in the dispatching component. While this generic exception does contain information about the root cause of the exception, it does not provide this in a format that can be used to base decisions on.

Therefore, the APIs should allow handlers to provide additional details that get transported to the client (using the message serializer). This object should be available on the CommandExecutionException, as well as the QueryExecutionException.

A Command/Query Handler can throw an exception that has the Command/Query ExecutionException in the cause-chain (or have an interceptor wrap it on its behalf) in order to provide these details.

@abuijze abuijze added this to the Release 4.2 milestone May 1, 2019

@abuijze abuijze self-assigned this May 1, 2019

abuijze added a commit that referenced this issue May 1, 2019

Added possibility to add application-specific details to HandlerExecu…

The CommandExecutionException and QueryExecutionException now provide
the option to add additional, application-specific, information to the
exception. This information will be send back to the dispatching
component, giving it the ability to make decisions based on this

Resolves #1079
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.