Schema generates multiple type qualifiers for Date, int, long data types

[aruld]

public class Employee {

  protected Date birthDt;
  protected String name;
  public Date getBirthDt() {
    return birthDt;
  }

  public void setBirthDt(Date value) {
    this.birthDt = value;
  }

  public String getName() {
    return name;
  }

  public void setName(String name) {
    this.name = name;
  }

  public static void main(String[] args) throws Exception {
    ObjectMapper mapper = new ObjectMapper();
    JsonSchemaGenerator generator = new JsonSchemaGenerator(mapper);
    JsonSchema jsonSchema = generator.generateSchema(Employee.class);
    System.out.println(mapper.writeValueAsString(jsonSchema));
  }
}

The code produces the JSON schema with redundant types for Date field.

{"type": "object", "properties": {
  "name": {
    "type": "string"
  },
  "birthDt": {
    "type": "number",
    "format": "UTC_MILLISEC",
    "type": "integer"
  }
}}

[aruld]

Deprecated JSON schema that comes with jackson-databind-2.2.2.jar works differently though. Here is the schema produced.

{"type": "object", "properties": {
  "birthDt": {
    "type": "number"
  },
  "name": {
    "type": "string"
  }
}}

[aruld]

Btw, this problem is not just with Date type. It occurs to long and int types.

{"type": "object", "properties": {
  "doubleProperty": {
    "type": "number"
  },
  "name": {
    "type": "string"
  },
  "floatProperty": {
    "type": "number"
  },
  "longProperty": {
    "type": "number",
    "type": "integer"
  },
  "birthDt": {
    "type": "number",
    "format": "UTC_MILLISEC",
    "type": "integer"
  },
  "intProperty": {
    "type": "number",
    "type": "integer"
  }
}}

[cowtowncoder]

Duplication was caused by unnecessary 'type' fields (although Jackson type id handler should actually be able to coalesce these but...)