jackson supports more than just json for serialization, XML and YAML come to mind. I'm currently working on something that only supports yaml (right now), it seems silly that the annotation's say @Json. It seems like being able to write @Creator would be better than @JsonCreator. I don't really mean getting rid of the existing ones though. Perhaps using "composed" annotations would be a better route, so that @JsonCreator would effectively become an alias for @Creator and both would work, also allowing people to compose their own.
jackson supports more than just json for serialization, XML and YAML come to mind. I'm currently working on something that only supports yaml (right now), it seems silly that the annotation's say
@Json
. It seems like being able to write@Creator
would be better than@JsonCreator
. I don't really mean getting rid of the existing ones though. Perhaps using "composed" annotations would be a better route, so that@JsonCreator
would effectively become an alias for@Creator
and both would work, also allowing people to compose their own.originally opened here https://github.com/FasterXML/jackson-core/issues/657#issue-757422633