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.

Sign up for GitHub

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

Jump to bottom

Katharsis client: Ability to add custom exception mapper #444

Open
ckarthik17 opened this issue Jul 26, 2017 · 0 comments
Open

Katharsis client: Ability to add custom exception mapper #444

ckarthik17 opened this issue Jul 26, 2017 · 0 comments

Comments

@ckarthik17
Copy link
Contributor

Currently, ExceptionMapperRegistryBuilder always adds KatharsisExceptionMapper as a default exception mapper for katharsis client.
So, even when I try to add an exception mapper by overriding getExceptionMapperRegistry(), always the default one is selected and my custom mapper is ignored.

All the related classes are sealed ExceptionMapperType, ExceptionMapperRegistry for extension.
Is there any workaround?
ckarthik17 pushed a commit to ckarthik17/katharsis-framework that referenced this issue Aug 7, 2017
katharsis-project#444 : Add default exception mapper only if customer…
fd150be 
… mapper not found for KatharsisMappableException
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ckarthik17