Skip to content

Swagger not working with this version strategy #2

Description

@ankool

Is there any example of springfox swagger working with this version strategy ?
I am using latest springfox library v2.9.2.

This version strategy creates mapping as below and is working as request navigates to different function based on version annotation value

V1:
"Mapped"{[/api/work/{vehicleId}],methods=[GET],produces=[application/json],custom=[com.work.version.service.VersionRequestCondition@390e814c]}"
 onto public org.springframework.http.ResponseEntity<com.work.models.WorkResponse>

V2:
"Mapped"{[/api/work/{vehicleId}],methods=[GET],produces=[application/json],custom=[com.work.version.service.VersionRequestCondition@1ed0128b]}"
 onto public org.springframework.http.ResponseEntity<com.work.models.WorkV2Response>

But with springfox we cannot create docket that maps to both version based on same path, method, and produces but different custom or response model.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions