Hi! I've noticed that the request-pattern.yaml schema contains the recently added file name property as

filename

while in

MultipartValuePattern

it is configured like this:

@JsonProperty("fileName") String filename

. Which one takes effect on Java side in this case, the parameter's name in the constructor or the value in the @JsonProperty annotation? (Pointing out the case mismatch in the schema and the annotation value.)

Good catch - it’s the JsonProperty parameter that defines how it’s deserialised and the name of the getter for serialisation, so the camel version

fileName

is correct, meaning the schema is wrong.

Thanks. That was my guess too. Would you like me to create an GitHub issue or a pull request with the fix?

PR would be great please