Multiple controllers with the same class level request mapping get ignored

[micksear]

Hi, I've been implementing this in my app and have noticed that if I have something like @RequestMapping("/api") in multiple controllers, only one gets processed. This is perfectly legal in Spring. If I refactor the class so it has no class level request mapping and instead adds that context path into each method's annotations, it displays them correctly.

[wkennedy]

I am able to reproduce this issue. I'll work on a fix!

[micksear]

Thanks. From what I can see, you will need to look up an existing Documentation object in the documents map in ApiParserImpl. processControllerDocumentation, and then add the additional methods to that. I can have a crack at it and issue a pull request if you like? It looks like the same issue will exist if @Api annotations are used.

[wkennedy]

Sure, if you want to take a swing at it and do a pull request, that would be great. I'll be more than happy to take a look at those changes and merge them.