geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6695) OpenAPI - Schemas are not working properly with a few issues
Date Tue, 19 Feb 2019 22:09:00 GMT


Romain Manni-Bucau commented on GERONIMO-6695:

[~ivanjunckes] the suspicious part in that model is that you have arrays of primitives, internals
of classes we should have been skipped way before so either you have in your model some runtime
object you don't want to serialize and use a not supported mapper to make it working (like
@SomeImplIgnore and therefore you need to use @Schema to get a clean openapi schema) or there
is a nasty bug. Starting from you endpoint you should be able to identify it, there is likely
a Class or ClassLoader in your objects.

> OpenAPI - Schemas are not working properly with a few issues
> ------------------------------------------------------------
>                 Key: GERONIMO-6695
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Ivan Junckes Filho
>            Assignee: Romain Manni-Bucau
>            Priority: Major
>         Attachments: image-2019-02-19-11-05-49-553.png, image-2019-02-19-11-07-02-967.png,
> 1 - Name of classes are not user friendly
> 2 - Internal system properties are showing up in the schema like factory, superclass,
typeParams... etc
> !image-2019-02-19-11-05-49-553.png!
> 3 - A lot of system classes are showing up as schemas and openapi should have only webapp
classes in the document. This even breaks swagger ui because it makes it super slow.
> !image-2019-02-19-11-07-02-967.png!
> The previous images come from swagger-ui.

This message was sent by Atlassian JIRA

View raw message