wkennedy
commented
11 years ago Unfortunately, this issue has come up a few times. The problem here is do to type erasure in Java generics. From Java generics entry in Wikipedia:
"Generics are checked at compile-time for type-correctness. The generic type information is then removed in a process called type erasure. For example, List will be converted to the non-generic type List, which ordinarily contains arbitrary objects. The compile-time check guarantees that the resulting code is type-correct. As a result of type erasure, type parameters cannot be determined at run-time."
That being said, they introduced in Swagger-Core the ability to handle generics using the @ApiOperation annotation, like so:
@ApiOperation.responseClass="foo.bar.A<foo.bar.B,foo.bar.C>"
I just tested this, but was not able to get it to work. I'm looking into why it's not generating the documentation correctly.
seawatts
When I have a controller method that returns List in the documentation it says the "Response Class" is:
Model | Model Schema List { empty(boolean optional) }
the controller method looks like this: @RequestMapping(method = RequestMethod.GET) @ResponseBody public List< GroupMember > getMembers() { ... myCode... }
Do you know why this could be?
Also, sorry this is a separate subject but you seem to be pretty responsive so I thought I would ask you, is there a way to gather the documentation from the JavaDocs in code? or do you have to use the @Api annotations?