I'm afraid the Jackson annotations don't provide enough flexibility for our use case. Without going into all details an example of what we do.
Given a class we want to expose through our api:
Class Entity
+String id
+String name
+Map<String,Object> propertySetA
+Map<String,Object> propertySetB
+Map<String,Object> propertySetB
make it look like
we need to:
1. Add the properties in the various sets to the model as property because the API user doesn't need to know about the propertySets A B C, it's an implementation detail, make it look like the properties belong to the entity.
2. Add Swagger description on all properties in the sets A B C. These descriptions (and types) are stored in a metadata repository
I'll see how hard it is to complete the custom converter implementation and send you a pull request so you can have a look.
Tim