[
https://issues.apache.org/jira/browse/OFBIZ-12426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451923#comment-17451923
]
ASF subversion and git services commented on OFBIZ-12426:
---------------------------------------------------------
Commit 421e0e7994ad5e69e6a60cb75a3c8715f0891c26 in ofbiz-plugins's branch
refs/heads/trunk from Michael Brohl
[ https://gitbox.apache.org/repos/asf?p=ofbiz-plugins.git;h=421e0e7 ]
Fixed: REST-API Plugin: Remove errors and warnings in generated openapi
documentation (OFBIZ-12426)
This fixes the following errors and warnings which are displayed by the
Swagger Editor (editor.swagger.io) when reading the generated openapi
documentation:
Errors fixed
* "Header parameters named "Authorization" are ignored. Use the
`securitySchemes` and `security` sections instead to define
authorization."
* "Structural error at paths./....parameters.0 should have either a
`schema` or `content` property"
the generated parameters from the service definition now have schema
entries generated
* the same applies to the WWW-Authenticate header in the responses
Warnings fixed
* "Header parameters named "Accept" are ignored. The values for the
"Accept" header are defined by `responses.<code>.content.<media-type>`."
> REST-API Plugin: Remove errors and warnings in generated openapi documentation
> ------------------------------------------------------------------------------
>
> Key: OFBIZ-12426
> URL: https://issues.apache.org/jira/browse/OFBIZ-12426
> Project: OFBiz
> Issue Type: Bug
> Components: rest-api
> Affects Versions: Trunk
> Reporter: Michael Brohl
> Assignee: Michael Brohl
> Priority: Major
>
> The generated openapi.json shows errors in [https://editor.swagger.io/]
> * "Header parameters named "Authorization" are ignored. Use the
> `securitySchemes` and `security` sections instead to define authorization."
> I guess the openapi generation must be changed, investigating...
> * "Structural error at paths./....parameters.0 should have either a `schema`
> or `content` property"
> the generated parameters from the service definition do not have a schema
> entry generated
> * the same applies to the WWW-Authenticate header in the responses
> It also shows warnings
> * "Header parameters named "Accept" are ignored. The values for the "Accept"
> header are defined by `responses.<code>.content.<media-type>`."
>
> This prevents, for example, the automatic client generation from within the
> editor.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
