[
https://issues.apache.org/jira/browse/ARIES-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272450#comment-17272450
]
ASF subversion and git services commented on ARIES-2032:
--------------------------------------------------------
Commit d219a9670cba99c217c309328d02ac0fd203da76 in aries-jax-rs-whiteboard's
branch refs/heads/master from Carlos Sierra Andrés
[ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=d219a96 ]
[ARIES-2032] ModelConverters global registry
ModelConverters per OpenAPI instance it work because Swagger
registers the ModelConverters globally, not per OpenAPI context, so
they are used internally regardless the context that registered
them. Therefore we are just adding every registered model converter to
the global registry.
> Aries JAX-RS OpenAPI integration picks up wrong classes for spec generation
> ---------------------------------------------------------------------------
>
> Key: ARIES-2032
> URL: https://issues.apache.org/jira/browse/ARIES-2032
> Project: Aries
> Issue Type: Bug
> Components: jax-rs-whiteboard
> Affects Versions: jax-rs-whiteboard-1.1.0
> Reporter: Thomas Driessen
> Priority: Minor
>
> If two endpoints, e.g., /item and /test, have a return type that is named the
> same, e.g., Metadata, but are from different packages, e.g.,
> io.jatoms.Metadata and io.jatoms.test.Metadata, then only one is picked up
> for the spec generation and therefore one endpoint will have false
> information in its description.
>
> I've created a sample repository showcasing this bug:
> [Sandared/osgi-openapi-example at openapi-bug
> (github.com)|https://github.com/Sandared/osgi-openapi-example/tree/openapi-bug]
>
> There two endpoint have return types that are named the same (Metadata), but
> are actually two classes from different packages
> (io.jatoms.osgi.openapi.model.test.Metadata and
> io.jatoms.osgi.openapi.model.Metadata).
> One Metadata class defines a field "id" and the other one "testid", however
> in the generated documentation only one of these is generated.
>
> Expected behavior would be that each endpoint documentation references its
> respective Metadata type.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
