wrong handling of bean properties in Records

[struberg]

Describe the bug
The spec requires to serialise attributs as "bean properties" according to the Java Bean 1.1 specification.
This seems not to be done in Records

I extended the RecordTest to have an additional bean attribute method as below

public record CarWithExtraMethod(String type, String color) {

    public String type() {
        return type;
    }

    public String name() {
        return color + " " + type;
    }

    public String getOtherName() {
        return color + " " + type;
    }

}

As result I get the following JSON: {"color":"green","getOtherName":"green skoda","type":"skoda"}.

This is imo wrong as the attribute name should only be otherName and not getOtherName.
Note that the method name() gets skipped as it is not a bean attribute (no getXxx nor isXxxx).

To Reproduce
Steps to reproduce the bug

Expected behavior
The resulting JSON should be {"color":"green","otherName":"green skoda","type":"skoda"}

System information:

• OS: OSX
• Java Version: 17
• Yasson Version: latest from today

[KyleAure]

I disagree with your assumption that the resulting JSON should be {"color":"green","otherName":"green skoda","type":"skoda"}
A Java Record IS NOT a Java Bean and should not be treated as one.
The components of a Java Record should be the record components and not bean properties.
Therefore, the resulting JSON should be {"color":"green","type":"skoda"}

So still a bug, but different underlying assumption.
I think it would be good to clarify this in the JSON-B API/SPEC since right now the default mapping section does not cover this case.
However, all other language surrounding Java Records suggests that only record components are mapped by default and therefore should apply here as well.

Thoughts?