How to Preserve Exact Field Capitalization in OpenAPI Schema

[ClaudiaIoana]

I have a Java model like this:

private String policyPlatType;
private SOMEPolicy[] SOMEPolicy;

public SOMEPolicy[] getSOMEPolicy() {
    return SOMEPolicy;
}

public void setSOMEPolicy(SOMEPolicy[] somePolicy) {
    this.SOMEPolicy = somePolicy;
}

public String getPolicyPlatType() {
    return policyPlatType;
}

public void setPolicyPlatType(String type) {
    this.policyPlatType = type;
}

When I generate the OpenAPI schema from this class, I get:

"policyPlatType": {
  "type": "string"
},
"sOMEPolicy": {
  "type": "array",
   ...
}

The problem is that the Java field is SOMEPolicy, but the generated OpenAPI schema uses sOMEPolicy. This creates an inconsistency between the documentation and the expected content of the requests.
The request is done as:

{
    "policyPlatType": ...
    "SOMEPolicy": ...
}

What I’m looking for is the OpenAPI equivalent of:

import com.fasterxml.jackson.databind.MapperFeature;
enable(MapperFeature.USE_STD_BEAN_NAMING);

In other words, how can I configure the OpenAPI so that the field is consistently represented as SOMEPolicy instead of sOMEPolicy?
I want to do this without annotations and changes on the class code. Is there any way in which this can be done?

[ClaudiaIoana]

If there is no way to achieve this, is there an alternative approach to replicate the behavior when MapperFeature.USE_STD_BEAN_NAMING is not enabled?

Here is the behavior I am referring to:

Jackson uses the class getters and setters to map attributes. When it encounters a field that starts with an uppercase letter, it will convert all leading uppercase letters to lowercase until it reaches the first lowercase letter.

For example, given a field named SOMEPolicyArray, Jackson will expect the JSON property to be named somepolicyArray.

So, the request would look like this:

{
    "policyPlatType": "...",
    "somepolicy": "..."
}

Is there any way to replicate this behavior in OpenAPI so that we can maintain naming consistency between the documentation and the Jackson deserialization behavior?