You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@camel.apache.org by Stephan <st...@yahoo.com> on 2016/02/11 11:22:09 UTC

Why does every swagger paramet gets an (empty) enum

I switched from Apache camel 2.16.0 to 2.16.2 and now all my parameters get
an additional empty enum even when no allowedValues are specified. Now
Swagger UI displays an empty dropdown for all dataTypes. I do not think that
is supposed to happen is it? Am I overseeing something?From
camel-example-swagger-java:
&lt;!-- this is a rest GET to view an user by the given id --&gt;&lt;get
uri="/{id}" outType="org.apache.camel.example.rest.User"&gt;   
&lt;description&gt;Find user by id&lt;/description&gt;    &lt;param
name="id" type="path" description="The id of the user to get"
dataType="integer"/&gt;    &lt;responseMessage message="The user that was
found"/&gt;    &lt;responseMessage code="404" message="User not found"/&gt;   
&lt;route&gt;      &lt;to
uri="bean:userService?method=getUser(${header.id})"/&gt;      &lt;filter&gt;       
&lt;simple&gt;${body} == null&lt;/simple&gt;        &lt;setHeader
headerName="Exchange.HTTP_RESPONSE_CODE"&gt;         
&lt;constant&gt;404&lt;/constant&gt;        &lt;/setHeader&gt;     
&lt;/filter&gt;    &lt;/route&gt;&lt;/get&gt;
This is what is generated, mind the empty enum:
"parameters" : [ {  "name" : "id",  "in" : "path",  "description" : "The id
of the user to get",  "required" : true,  "type" : "integer",  "enum" : [ ]}
],
It is also not possible to specify the allowedValues using xml or am I doing
something wrong?



--
View this message in context: http://camel.465427.n5.nabble.com/Why-does-every-swagger-paramet-gets-an-empty-enum-tp5777585.html
Sent from the Camel - Users mailing list archive at Nabble.com.