Rüdiger zu Dohna

The type of API that I've had in mind would even more hide the fact that we are doing messaging, i.e. I'd define a business interface: ```java @MessageApi public interface...

@dblevins: Something for the 'Related' section that I'm sure you'll love to hear about: the MP GraphQL team is working on supporting Stereotypes (and more), too. We try to extract...

I was curious, so I looked it up: [stereotype](https://www.etymonline.com/word/stereotype) translates as solid-print; the meaning 'two' is just a coincidence. I'm fine with calling it MetaTypes, esp. as stereotypes applied to...

@mkarg : Thanks for the hint ;-) My use-case (as stated in #839) is that I want to map Problem Details (http response entities describing the exact cause for a...

@chkal : That's a great idea; it still requires the `@ProblemAware` artifact, but it's better than unwrapping the `ResponseProcessingException`. I think I'll implement that. An option to not wrap exceptions...

I like to map exceptions to rfc-7807 compliant bodies on the server side and/or back to exceptions on the client side (note: they don't have to be the same exception,...

Building the response `Problem` object by hand looks like a lot of boiler plate code to me. I think throwing a specific business exception and have that automatically mapped to...

@dhh1128: The post has been deleted!?! What are the arguments?

It's an old dispute going forth and back: should we prevent good things just because they can be misused? Don't get me wrong: this dispute is difficult and there is...

@mkarg : you wanted to close this issue 😁 BTW: four years ago, I started to write such a [library](https://github.com/t1/problem-details) and a [blog](https://www.codecentric.de/wissens-hub/blog/rfc-7807-problem-details-with-spring-boot-and-jax-rs) about this, if anybody happens to be...