Issue validating parameters resulting in java.lang.NullPointerException

Issue #173 resolved
Greg Zealley created an issue

Hi,

In attempting to validate an API using Swagger definition in OpenApi v3. I am getting the following error:

java.lang.NullPointerException
    at com.atlassian.oai.validator.parameter.ParameterValidators.validate(ParameterValidators.java:43)
    at com.atlassian.oai.validator.interaction.RequestValidator.lambda$validatePathParameter$13(RequestValidator.java:402)
    at java.util.Optional.map(Optional.java:215)
    at com.atlassian.oai.validator.interaction.RequestValidator.validatePathParameter(RequestValidator.java:402)
    at com.atlassian.oai.validator.interaction.RequestValidator.lambda$validatePathParameters$11(RequestValidator.java:385)
    at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
    at java.util.Iterator.forEachRemaining(Iterator.java:116)
    at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
    at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
    at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
    at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
    at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)

This is the relevant part of the Swagger JSON:

  "paths": {
    "/apis/v1/api_name/datasets/{datasetId}/datafiles": {
      "post": {
        "tags": [
          "api_name"
        ],
        "summary": "The API summary",
        "operationId": "createDatafile",
        "parameters": [
          {
            "in": "path",
            "name": "datasetId",
            "required": "true",
            "description": "Dataset Unique Resource Identifier\nExample: some_example\n",
            "schema": {
              "type": "string"
            }
          }
        ],

and this is the endpoint called in the test:

/apis/v1/api_name/datasets/some_dataset/datafiles

Am I doing something wrong? Thanks : )

Comments (4)

  1. Greg Zealley reporter

    Update - sine upgrading to use v2.0.2 this issue has been resolved.

    Using v2.0.2 did complain about incorrect server specification in Swagger (which v2.0.1 didn't) and once that was resolved, the above issue did not then re-occur.

    Is there a version history list for this anywhere?

    Thanks,

  2. James Navin

    Hi Greg.

    There is a RELEASE-NOTES.md in the project root dir that contains details of the changes in each version release.

    I'll mark this issue as resolved - if you have other issues feel free to re-open or create a new one.

    Cheers.

  3. Log in to comment