https://bz.apache.org/bugzilla/show_bug.cgi?id=65256
--- Comment #3 from romain.manni-bucau <rmannibu...@gmail.com> --- Hi, I think it is a bug to not list interfaces. Spec quote considers interfaces as "class" in its wording: > extends / implements one those classes Not returning interfaces breaks some serious number of use cases, typically all cases where annotations are used for scanning and are put on interfaces (often it is then implemented thanks a proxy, even for Servlet case ;)) and cases where annotations host the "spec" of the API and are read from the scanned set to deduce it (meta annotation API alike). So overall I see that interface scanning is: 1. used 2. compaitble with current spec wording (even allowed IMHO) 3. supported by tomcat (before the last commit), jetty and undertow So it looks legitimate to rather ask the spec to phrase it explicitly rather than breaking user with next release and then get the feature back later (I assume spec will explicit interfaces are enabled). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
