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

Shankar Ramamoorthy edited comment on CAMEL-15503 at 4/23/21, 1:00 AM:
-----------------------------------------------------------------------

This is marked as an Improvement. Does that mean there is some way to produce 
correct openapi v3 schema?

Been looking through the code in camel-openapi-java. 

`org.apache.camel.openapi.RestModelConverters` has method 
`readClassOas30(Oas30Document, Class<?>)` but there is no code to actually 
convert a POJO into OAS schema definitions. That's why all classes end up in 
the generated schema like `POJO \{"type": "POJO"}.`.

Maybe I'm missing something.


was (Author: maqroll):
This is marked as an Improvement. Does that mean there is some way to produce 
correct openapi v3 schema?

> Apache Camel camel-openapi-java Schema Definitions not generating correctly
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-15503
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15503
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-openapi-java
>    Affects Versions: 3.4.3
>            Reporter: Kate Hennessy
>            Assignee: Viral Gohel
>            Priority: Major
>             Fix For: 3.10.0
>
>         Attachments: camelOpenAPITest.zip
>
>
> Classes defined in RestDefinition _type_ and _outType_ are not generating 
> correctly in openapi schema. This worked in the older older 
> camel-swagger-java component, the schema was generating with all object 
> definitions correctly. 
>  
> Please see this question on stack overflow for more details. 
> [https://stackoverflow.com/questions/63691670/apache-camel-camel-openapi-java-schema-definitions-not-generating-correctly]
>  
> Sample project with the issue happening is attached. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to