Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow creation of HandlerExecutionExceptions without stacktrace
See original GitHub issueEnhancement Description
Since HandlerExecutionExceptionsare essentially carriers for error codes, their stacktrace is not of great value in common scenarios of passing error codes between JVMs. For this reason, I think it would be sensible to add the writableStackTrace parameter to the constructors of HandlerExecutionExceptions. That way a programmer can decide if stacktrace is important enough to pay the penalty of creating it.
Related discussion with a bit more details: https://discuss.axoniq.io/t/handlerexecutionexception-stacktrace-necessary/3453
Current Behaviour
At the moment there is no writableStackTrace parameter in the API of HandlerExecutionException constructors.
Tnx
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing this issue, as it has been resolved in pull request #1905. Thanks for drafting up the description and for providing the solution @dmurat!
Here is the PR proposal: https://github.com/AxonFramework/AxonFramework/pull/1905 Tnx