Conor Roche

i have now added support for @beanparam to the carma public fork https://github.com/Carma-Public/swagger-jaxrs-doclet

@cviebig ive just committed support for json view to https://github.com/Carma-Public/swagger-jaxrs-doclet ive added a test fixture for it too that uses interfaces and classes for the view classes based on the...

ive a fork that also supports this https://github.com/Carma-Public/swagger-jaxrs-doclet using the -crossClassResources option, this fork is for swagger 1.2 btw.

@bobpiece thanks i have that (support for sub resources on the cross class parser) on my roadmap but will bring it forward to the 1.0 release and try to work...

i have now committed support for sub resources to the cross class parser and removed the old one so there is now a single parser. the old doclet option to...

ive added support for this in my fork https://github.com/Carma-Public/swagger-jaxrs-doclet via the swaggerUiPath doclet option

my fork https://github.com/Carma-Public/swagger-jaxrs-doclet (which is for the swagger 1.2 spec and which i use for a large api https://api-dev.car.ma/apidoc/ref/index.html) supports this as well as per status code response types by...

@cviebig can you give me an example of what you mean by request objects? I havent looked at Jsonview in terms of seeing how hard that will be, i did...

do you mean something like this: ``` @POST /** * @inputType com.myclass.SmallNote */ public Response createNote(BigNote note) ``` where you want the generated docs to only describe the fields from...

there can only be one body param e.g. non query/path param in post/put method signatures so no need for the param name. you can use @JsonIgnoreProperties(ignoreUnknown = true) on the...