Re: Error in generated code (Java JAX-RS, serverside) for extended models

Hey Ron, it was my fault. I made an error in my swagger definition that caused no syntax error and the generated subclass had the correct extension but were empty. Now I correced my mistake and the subclasses are generated correctly. Now I have another iussue. I am using specification 2.0 and al

Error in generated code (Java JAX-RS, serverside) for extended models

There is a big bug in code generation for Java JAX-RS (serverside) when extended models are used. For example I have a Sawgger definition like this: ... MyModel: type: object discriminator: type properties: type: type: string enum: - MyExtendedModel1

Swagger server side code generation with type-mappings: How to add converter?

Hello, I want to use my own Date (MyDate) implementation instead of java.util.date or yodatime or someting like that. Therefore I use the switches --type-mappings and --import-mappings during server side code generation (Jax-RS). The generated code is ok but it does not work out of the box, be

Swagger generated server code: enum serialization is incorrrect

Hello, I defined some String enums in my swagger file and generated server side code (Jax-RS) out of it. The "swagger eums" are generated as Java enums, for example: /** * Gets or Sets status */ public enum StatusEnum { PLANED("planed"), STARTED("started"), FINISHED("finished"); pr

Re: Generated server code (JAX RS) can't handle generated enums

Hello, I have found out, that the response does not contain null for enums values, but it contains the name of the enum constant (value in upper case) instead of the string defined for the enum constant (lower case). And the client side code (also generated) tries to find the enum constant matc

Generated server code (JAX RS) can't handle generated enums

Hello at all, I have a *swagger.yaml* where I also define some enums, like this: type: object properties: id: type: integer status: type: string enum: - started - finished With that definiiton I generate server code for JAX RS and the

How to generate "specific" response classes in Java (JaxRS)?

Hello, is it possible to generate response classes with a specfic name so you can easily see which response is the answer for which operation? For example I have three paths *ping1*, *ping2*, *ping3* where the response code is always 200 and some etxra data. Swagger generates three class in fol

Re: How to define a set of standard parameters for each path item

eger > post: > parameters: > - $ref: '#/parameters/session' > responses: > '200': > description: sample > > > > On 13/06/2017, 12:13, "'Philipp' via Swagger" < > swagger-sw...@g

Re: How to define a set of standard parameters for each path item

schrieb Ron: > So again, you can’t define groups of parameters. > You can define individual parameters, and reference them one by one from the > different paths. >   > Take a look at > https://github.com/OAI/OpenAPI-Specification/blob/master/guidelines/REUSE.md > for more de

Re: How to define a set of standard parameters for each path item

I have a set of data, that should be send as parameter in every single path and I only want to describe them only once. It does not matter if it is designed as a group of parameters that can be referenced by every path, or the data is included in one object and I describe one referencable param

Re: How to define a set of standard parameters for each path item

I know, that's why I tried to use a body parameter with a schema/object definition as you can see in my second example. But till now I am not able to write a definition which the editor accepts when I define the parameter outside the path/request. If I place it into the request everything is fin

How to define a set of standard parameters for each path item

Hi, I have a set of parameters, that should be used by nearly every path item as standard. I only want to define these parameters once and use them, when I need them, by writing one reference to the set of my parameters. How to write it down in Swagger? I tried a lot of tinks, but nothing was a

Re: Problems with parsing datetime on server side

Ok, I created ticket 3648 . Am Donnerstag, 25. August 2016 14:01:11 UTC+2 schrieb Philipp: > > Hello at all, > > I have a swagger definition like this: > > /services: > get: > parameters: > - name: begin > in: