"properties" property implies "type": "object"

[fixpunkt]

When trying to generate a POJO for this schema:

{
    "title": "AggregatedIncidentDateEntity",
    "properties": {
        "date": {
            "type": "string",
            "format": "date-time"
        },
        "date_ms": {
            "type": "integer",
            "description": "date in milliseconds"
        },
        "count": {
            "type": "integer"
        }
    }
}

no POJO is generated. However, after adding "type": "object" to the toplevel object, a POJO will be generated. Since there is a properties property, the instance should be recognized as being of object type automatically. Schemas of this style are used as examples in the Spec (cf. http://json-schema.org/latest/json-schema-validation.html#anchor64), so this should be supported.

[joelittlejohn]

I don't think those schema examples from the spec are intended to be complete (and valid) schema files, I think they may simply be snippets that include the relevant rules and omit other noise. I like the idea of making this change though as think it would avoid quite a bit of confusion.

[fixpunkt]

Yeah, this took me some time to figure out because jsonschema2pojo will just silently ignore these schemas, which left me scratching my head for a few hours. Producing a warning might be an alternative as well. To be completely honest, I didn't find any conclusive information in the spec on whether the above would be correct schema or not.