Similar behavior occurs when enum name is defined in camel-case and during code generation it gets value for the original name used in api and name in upper case. When this is (de)serialized it does not use this value but name instead.

Can be fixed also with @JsonCreator annotation on the generated fromValue(String) method.

Currently the only workaround seems to be to override the enumOuterClass.mustache file locally with the said annotation in place

@arnis87 Can you please provide an example? Thanks!

Hmm, This was some time ago and do not remember exact details but something like this:
I have json defined as

...
"Blacklisted": {
            "$ref": "#/components/schemas/BlacklistType"
          },
...
"BlacklistType": {
        "enum": [
          "NotListed",
          "Denied",
          "Warning"
        ],
        "type": "string"
      }

This is then generated into java:

public enum BlacklistType {
  
  NOTLISTED("NotListed"),
  
  DENIED("Denied"),
  
  WARNING("Warning");

  private String value;

  BlacklistType(String value) {
    this.value = value;
  }

  @Override
  public String toString() {
    return String.valueOf(value);
  }

  public static BlacklistType fromValue(String value) {
    for (BlacklistType b : BlacklistType.values()) {
      if (b.value.equals(value)) {
        return b;
      }
    }
    throw new IllegalArgumentException("Unexpected value '" + value + "'");
  }
  
}

Notice that the value for the java enum is same as in the json definition and name is all caps. However when request is made filling the object with enum setBlacklisted(BlacklistType.NOTLISTED) it gets serialized into string:
"Blacklisted" : "NOTLISTED", but due to JSON contract the expected value is ins serialized string is NotListed

Is this bug solved yet? If yes, which release has it?