anyOf validation failing if reference schema has additionalProperties property

[marutha]

{
    "title" : "Update Vehicle",
    "$schema" : "http://json-schema.org/draft-04/schema#",
    "id" : "post_vehicle.json",
    "type" : "object",
    "properties" : {
        "content" : {
            "type" : "object",
            "anyOf" : [
                {
                    "$ref" : "post_car.json"
                },
                {
                    "$ref" : "post_jet.json"
                }
            ]
        }
    },
    "required" : ["content"],
    "additionalProperties" : false
}

The post_car.json has the below

{
    "title" : "Update car",
    "$schema" : "http://json-schema.org/draft-04/schema#",
    "id" : "post_car.json",
    "type" : "object",
    "properties" : {
        "steering_type" : {
            "type" : "object",
            "properties" : .......
        }
...........
    },
    "additionalProperties" : false
}

The validation is failing with above and passing when I remove the below lines in post_car.json,

    "additionalProperties" : false

if I am right if the schema validation fails in post_car.json, it should process for post_jet.json, this behaviour is happening only when the above property "addtionalProperties" is present.

[andreineculau]

@marutha thanks for the report, but please provide full examples of schemas + instance, along with the failing message

[marutha]

I will close this as of now