Allow use of abstract classes in Quarkus REST in the same way as inte…

…rfaces Fixes: quarkusio#41567 (cherry picked from commit c56532c)
gsmet · Aug 14, 2024 · 46f4b6b · 46f4b6b
1 parent 56a41b1
commit 46f4b6b
Showing 1 changed file with 15 additions and 0 deletions.
diff --git a/...n/java/org/jboss/resteasy/reactive/common/processor/scanning/ResteasyReactiveScanner.java b/...n/java/org/jboss/resteasy/reactive/common/processor/scanning/ResteasyReactiveScanner.java
@@ -262,6 +262,21 @@ public static ResourceScanningResult scanResources(
             }
         }
 
+        // handle abstract classes
+        scannedResources.values().stream().filter(ClassInfo::isAbstract).forEach(abstractScannedResource -> {
+            Collection<ClassInfo> allSubclasses = index.getAllKnownSubclasses(abstractScannedResource.name());
+            if (allSubclasses.size() != 1) {
+                return; // don't do anything with this case as it's not evident how it's supposed to be handled
+            }
+            ClassInfo subclass = allSubclasses.iterator().next();
+            if (!scannedResources.containsKey(subclass.name())) {
+                scannedResources.put(subclass.name(), subclass);
+                scannedResources.remove(abstractScannedResource.name());
+                scannedResourcePaths.put(subclass.name(), scannedResourcePaths.get(abstractScannedResource.name()));
+                scannedResourcePaths.remove(abstractScannedResource.name());
+            }
+        });
+
         Map<DotName, String> clientInterfaces = new HashMap<>(pathInterfaces);
         // for clients it is enough to have @PATH annotations on methods only
         for (DotName interfaceName : interfacesWithPathOnMethods) {