camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan <>
Subject Why does every swagger paramet gets an (empty) enum
Date Thu, 11 Feb 2016 10:22:09 GMT
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
&lt;!-- this is a rest GET to view an user by the given id --&gt;&lt;get
uri="/{id}" outType=""&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(${})"/&gt;      &lt;filter&gt; 
&lt;simple&gt;${body} == null&lt;/simple&gt;        &lt;setHeader
&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:
Sent from the Camel - Users mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message