Anders Storsveen

This is because the implementation used by the problem-detail library, has StatusType in the POJO, and registers a Jackson-Module to the ObjectMapper, that provides code to serialize the StatusType class...

The biggest technical issue here is that without a declarative description of the serialization rules in the POJO or in the Jackson-Module/ObjectMapper, it's very hard to deduce what the actual...

This is how I fixed this running without spring (this falls back on the default behavior except for on ERROR_NOT_HANDLED aka -32001): ` public class MyHttpStatusCodeProvider implements HttpStatusCodeProvider { private...

I managed to fix this by doing what I suggested above. Why isn't exceptions serialized and deserialized like all other objects?

Ok, I figured out a way to do this, but it's not very pretty. I used ThreadLocal to set a variable on the current thread, I then read that variable...

After some more digging, I found another commit that seems to add functionality to _not_ log that line at all.with "setShouldLogInvocationErrors".

I just upgraded to a newer version, and had to look through all the commits on JsonRpcServer to confirm that I wasn't crazy. Having the readme reflect the actual latest...

What is even the point of the code examples that are generated? They contain no models, but do refer to them...

We are also experiencing this bug. Would be great to get this merged!

I'm also having the same issue. The workaround adds the @Valid at the correct place, but it still includes the @Valid at the wrong place, which breaks it.