RSPEC-2260 - Java parser failure

Rules and Languages
1

Hi! I got today this Java parser failure rule triggered and it is hard to tell what is the actual issue. I have this record

import com.fasterxml.jackson.annotation.JsonProperty;

public record Person (@JsonProperty("person_id") String id,
                      @JsonProperty("person_name") String name){
}

And it returns a “Parse error” on line “public record Person”

The description of the rule says:
When the Java parser fails, it is possible to record the failure as a violation on the file. This way, not only it is possible to track the number of files that do not parse but also to easily find out why they do not parse.

It is not clear if it is actually a vulnerability or if it is a problem of the scanner reading the java file.

I converted the record to a regular class like the following and the issue went away

import com.fasterxml.jackson.annotation.JsonProperty;

public final class Person {
    @JsonProperty("person_id")
    private final String id;
    @JsonProperty("persin_name")
    private final String name;

    public Person(String id,
                      String name) {
        this.id = id;
        this.name = name;
    }

    public String getId() {
        return id;
    }

    public String getName() {
        return name;
    }
}

Thanks!

2

Hi,

Please specify what product and version you’re using.

  • SonarQube Cloud?
  • SonarQube Server / Community Build - which version?
  • SonarQube for IDE - which IDE/version?
    • in connected mode with SonarQube Server / Community Build or SonarQube Cloud?

I’m pretty sure that parsing Java records have been supported for many years, which suggests that an outdated version of SonarQube is being used.

1 Like
3

Hi Scott. From what I see, it is Sonar Server Enterprise 9.9.3

4

Hi,

A lot has changed in the last 2+ years, including our Java parser. Please upgrade to a current version and see if this is still replicable.

 
Thx,
Ann

1 Like