Forum Discussion

BenjaminJelli's avatar
BenjaminJelli
Regular Visitor
4 years ago
Solved

Specifying Encoding For Form Data Parameters

Hello,   My question is specific to jaxrs2 integration and could be summarised as the following: "What does the path look like to fleshing out jaxrs2 integration such that it can be used to genera...
Swagger Core
swagger-jaxrs2
  • frantuma's avatar
    frantuma
    4 years ago

    Hi,

     

    I am not sure I fully understand what you mean with:

     

    "What does the path look like to fleshing out jaxrs2 integration such that it can be used to generate all aspects of the OpenAPI 3.0 specification, esp. with regards to its priority relative to other aspects of the Swagger Core project?"

     

    But if I get this right you are looking for some refactor of the module to better handle processing/resolving; while this would be indeed good, we don't have planned it for short term, as always any help is more then welcome.

     

    For your specific question/comment, many thanks for the PR providing a possible solution; this has been replaced by https://github.com/swagger-api/swagger-core/pull/3696 which adds support for `@Parameter` resolving, please give it a try and see if it solves your issue (if not, please add comments/follow ups to https://github.com/swagger-api/swagger-core/issues/3643)

frantuma's avatar
frantuma
Staff
4 years ago

Hi,

 

I am not sure I fully understand what you mean with:

 

"What does the path look like to fleshing out jaxrs2 integration such that it can be used to generate all aspects of the OpenAPI 3.0 specification, esp. with regards to its priority relative to other aspects of the Swagger Core project?"

 

But if I get this right you are looking for some refactor of the module to better handle processing/resolving; while this would be indeed good, we don't have planned it for short term, as always any help is more then welcome.

 

For your specific question/comment, many thanks for the PR providing a possible solution; this has been replaced by https://github.com/swagger-api/swagger-core/pull/3696 which adds support for `@Parameter` resolving, please give it a try and see if it solves your issue (if not, please add comments/follow ups to https://github.com/swagger-api/swagger-core/issues/3643)