type: file is not allowed in body parameter

The 2.0 spec says

An additional primitive data type “file” is used by the Parameter Object and the Response Object to set the parameter type or the response as being a file.

The JSON schema for OpenAPI 2.0 allows type: file in the schema for a response body.

        "schema": {
          "oneOf": [
            {
              "$ref": "#/definitions/schema"
            },
            {
              "$ref": "#/definitions/fileSchema"
            }
          ]

but fileSchema is not included in the schema for parameter with in: body:

    "bodyParameter": {
      "type": "object",
      "required": [
        "name",
        "in",
        "schema"
      ],
      "patternProperties": {
        "^x-": {
          "$ref": "#/definitions/vendorExtension"
        }
      },
      "properties": {
        "description": {
          "type": "string",
          "description": "A brief description of the parameter. This could contain examples of use.  GitHub Flavored Markdown is allowed."
        },
        "name": {
          "type": "string",
          "description": "The name of the parameter."
        },
        "in": {
          "type": "string",
          "description": "Determines the location of the parameter.",
          "enum": [
            "body"
          ]
        },
        "required": {
          "type": "boolean",
          "description": "Determines whether or not this parameter is required or optional.",
          "default": false
        },
        "schema": {
          "$ref": "#/definitions/schema"
        }
      },

Thus, the following OpenAPI document does not pass schema validation.

swagger: "2.0"
info:
  title: Issue 1226
  description: 'type: file not allowed for body parameter '
  version: "1"
basePath: /issue-1126
paths:
  /issues:
    post:
      summary: Create a resource from the body
      consumes:
      - application/zip
      produces:
      - application/zip
      parameters:
      - name: content
        in: body
        required: true
        description: A zip file of the contents.
        schema:
          type: file
      responses:
        201:
          description:  Created.
          schema:
            type: file
          headers:
            Location:
              description: location of the new resource
              type: string

[jemerald]

Found a temporary workaround from https://github.com/OAI/OpenAPI-Specification/issues/326

schema:
  type: string
  format: binary

However, the code generation would produce byte[] instead of nicer Stream class.

[darrelmiller]

Moving forward, I would suggest that tooling use stream for this description and where a maxLength is provided byte[] could be used instead.