You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The swagger generator plugin will correctly understand that it should treat this endpoint as a "binary" endpoint.
(The other side will have to manually craft the message which I handwrite in the client anyways)
MultiPart is org.glassfish.jersey.media.multipart.MultiPart
For some reason the generator decides to include Model Spec of org.glassfish.jersey.media.multipart.MultiPart.
Due to me overriding the requestBody the Model of MultiPart is not used anywhere but it is still included in the spec. This is not desired as it generates a few very confusing Model Classes in any client generating a client from the spec.
This is one such model that should really not be generated:
I have a jaxrs endpoint which has to accept a complicated multipart message using Jersey.
This is the endpoint:
The swagger generator plugin will correctly understand that it should treat this endpoint as a "binary" endpoint.
(The other side will have to manually craft the message which I handwrite in the client anyways)
MultiPart is org.glassfish.jersey.media.multipart.MultiPart
For some reason the generator decides to include Model Spec of org.glassfish.jersey.media.multipart.MultiPart.
Due to me overriding the requestBody the Model of MultiPart is not used anywhere but it is still included in the spec. This is not desired as it generates a few very confusing Model Classes in any client generating a client from the spec.
This is one such model that should really not be generated:
The genrate should completly ignore any "models" in the org.glassfish.jersey.media.multipart and treat them as If they were "InputStream".
The text was updated successfully, but these errors were encountered: