[jira] [Commented] (CAMEL-11088) camel-swagger-java: schema objects in definitions could not be referenced

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947039#comment-15947039 ] 

Claus Ibsen commented on CAMEL-11088:
-------------------------------------

You are welcome to provide a github PR with a backport of this to the 2.17.x branch

As the next 2.17.x release is going to be the last so this may otherwise slip this release and you wont have a fix in it.

> camel-swagger-java: schema objects in definitions could not be referenced 
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-11088
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11088
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-swagger
>    Affects Versions: 2.17.6
>            Reporter: Yangyang Li
>            Priority: Minor
>
> Reproduct steps:
> 1. we have a type A, and it has a field b with type B.
> 2. there are two camel rest endpoint a and b, type attribute of endpoint a is A, and type attribute of endpoint of b is B.
> 3. when RestSwaggerReader.java parse the endpoint a at first, and parse the endpoint b later.
> 4. in the generated swagger document, the "schema" of parameter object of endpoint b could not $ref to the definition object B in definitions module.
> Maybe this issue is caused by the code "oldExt = oldModel.getVendorExtensions().get("x-className") == null;" of appendModels method of RestSwaggerReader.java of camel 2.17.x.
> This code has been changed to "oldExt = oldModel.getVendorExtensions().get("x-className") != null;" of camel 2.18.x.
> So I file jira ticket to request to fix this issue in camel 2.17.x too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)