Ability to add custom exception mapper

[remmeier]

orignally from @ckarthik17

Currently, ExceptionMapperRegistryBuilder always adds CrnkExceptionMapper as a default exception mapper for crnk 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?

[alexander-matthiesen]

Same for me, are there any updates? For the exceptions that are not mapped by the default ExceptionMapper like 415, my ExceptionMapper does what it should.